decomposer: generate deliverable files for Inspect the single_agent template and target repository conventions to identify the required project structure, configuration, interfaces, and implementation patterns for the application landing zone agent.; Define the application landing zone agent's behavior, input and output contracts, document-generation workflow, and architecture-diagram requirements using the extracted template conventions.; Validate the implemented application_landing_zone_agent by running repository tests and checking the TSD document generation, draw.io diagram generation, agent packaging, configuration, and committed implementation against the defined contracts.; Commit and push the validated application_landing_zone_agent implementation to the target repository.

This commit is contained in:
2026-08-31 14:42:05 +00:00
parent 14a36dc002
commit de9facf433
15 changed files with 373 additions and 2 deletions

View File

@@ -1,3 +1,26 @@
# crucible-agent-build-phase-2
# Application Landing Zone Agent
Auto-generated agent: build-phase-2
A deterministic, dependency-light agent that turns application requirements into a Technical Solution Design (TSD) and an editable draw.io architecture diagram.
## Quick start
```bash
python -m application_landing_zone_agent.cli \
--input examples/application.json \
--output-dir build/example
```
The command writes `tsd.md` and `architecture.drawio` and validates both before returning success. The package also exposes `LandingZoneAgent.generate(requirements)` for embedding.
## Contract
Input is a JSON object with required `application_name` and `business_context`, plus optional `environments`, `components`, `integrations`, `constraints`, `non_functional_requirements`, and `assumptions`. Output is a `GenerationResult` containing Markdown TSD text, draw.io XML, and a validation report. See `docs/agent-specification.md`.
## Development
```bash
python -m unittest discover -s tests -v
python -m application_landing_zone_agent.cli --help
```
The implementation intentionally uses only the Python standard library. Configuration is JSON (`config/default.json`) so the same contract works in CI and local tooling.