Design is now approved before any infrastructure code is written (ADR-0005). A new target-architect Specialist produces one graph of Elements, Relationships and Checks; the diagram is rendered from it, deployment guidance must account for every Check, and validation gives a verdict per Check. Requirements, components, products and recommendations carry ids in data files, and a submission with a gap in the Requirements chain is refused. Also in this commit: - Customer cases group Executions, with an intent history per case - lesson candidates are captured when an Execution ends - evaluation gains chain, verdict, judged and interactive checks, and per-case thresholds - Terraform providers are cached between checks - the requirements analyst proposes defaults instead of asking - the legacy-baseline case and the checks that only read it are removed - ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed - plans for iterations 4 to 7 under .agents/plans/ Unproven with a real model: no evaluation run has completed on this design. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Step 2 — Implementation Detail
app/workflows/chain.pydefines the data files and a checker for each. Each checker returns one entry per fault, so a Specialist can fix and resubmit.- New required attachments (
DATA_CHECKSinapp/workflows/deliverables.py):requirements.jsonon requirements:{id, kind, text}, kind functional or non_functional, ids unique.components.jsonon the technical decomposition:{id, name, requirements}. This replaced the component table contract from iteration 4 step 4.products.jsonon product selection:{component, product}, one for every component.recommendations.jsonon design recommendations:{id, pillar, text, components}.
check_submissiontakes the Deliverables being built on (upstream), so links are checked across Deliverables: a component may only serve a real requirement, a product may only be selected for a real component, a recommendation may only name real components.- The formats live in a new Skill,
skills/requirements-chain/SKILL.md, assigned inproviders/gcp.yamlto every role that writes or reads one.
Changed from the plan:
products.jsonwas added. The plan's rule "a selected product appears on no Element" needs the selection as data.- Only functional requirements must be served by a component at the decomposition. A non-functional requirement often constrains the whole workload, so it is held to a stricter rule later: it must be the source of a Check (step 5).
Tests: tests/execution/test_requirements_chain.py, "the links before the graph".