agents/crucible-agent-build-phase-2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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.

Browse Source
This commit is contained in:
demo-bot
2026-08-31 14:45:15 +00:00
parent 576c4050be
commit 0060bdd426
14 changed files with 226 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@@ -1,26 +1,20 @@
# Application Landing Zone Agent
A deterministic, dependency-light agent that turns application requirements into a Technical Solution Design (TSD) and an editable draw.io architecture diagram.
A deterministic, dependency-light agent that converts 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
python -m landing_zone_agent.cli --requirements examples/requirements.json --output-dir out
python -m unittest discover -s tests -v
```
The command writes `tsd.md` and `architecture.drawio` and validates both before returning success. The package also exposes `LandingZoneAgent.generate(requirements)` for embedding.
The CLI writes `tsd.md`, `architecture.drawio`, and `manifest.json`. The generator does not call an LLM or cloud APIs; it produces a reviewable baseline that can be refined by an architect.
## 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`.
Input is JSON with `application_name`, `business_context`, `environments`, `data_classification`, `availability_target`, and optional `components`, `integrations`, and `constraints`. Output is a TSD Markdown document, draw.io XML, and a manifest containing assumptions and validation results. See `docs/agent-specification.md`.
## Development
## Configuration
```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.
`config/agent.json` contains defaults and capability declarations. Configuration is loaded by `landing_zone_agent.config.load_config`; no secrets are stored in the repository.