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:42:05 +00:00
parent 14a36dc002
commit de9facf433
15 changed files with 373 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/repository-conventions.md Normal file
View File

@@ -0,0 +1,21 @@
# Repository convention discovery (Step 0)
No template or target URL was supplied with the request, so this repository records the conventions used as the implementation baseline rather than claiming an external inspection. The baseline follows a conventional Python agent layout: `src/` package, `tests/` unittest suite, `config/` JSON configuration, `docs/` contract material, and a CLI entry point.
## Required structure
- `src/application_landing_zone_agent/`: importable implementation and CLI.
- `tests/`: unit and contract tests runnable with `python -m unittest discover -s tests`.
- `config/default.json`: checked-in, dependency-free configuration.
- `docs/agent-specification.md`: behavior, contracts, workflow, and validation.
- `examples/`: human-reviewable input fixture.
- `pyproject.toml`: package metadata and console script.
## Conventions extracted for this build
- Public behavior is exposed through a small class (`LandingZoneAgent`) and a CLI adapter.
- Input/output boundaries are typed dataclasses and JSON/Markdown/XML files.
- Generation is deterministic: stable IDs, ordering, and formatting make output reviewable in source control.
- Validation happens before files are written and is also available as a public function.
- Diagram output is native draw.io `mxfile` XML, not an image or proprietary binary.
- Errors are actionable `ValidationError`/`GenerationError` exceptions; CLI maps them to a non-zero exit code.