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.2 KiB
1.2 KiB
Step 5 — Implementation Detail
chain_gaps in app/workflows/target_architecture.py lists every place the Requirements chain stops; check_target_architecture runs it at submission, so a Target architecture with a gap is refused with each gap named.
A gap is:
- a component with no Element;
- a non-functional requirement that is the source of no Check;
- a functional requirement that is the source of no Check and is served by no component with an Element;
- a selected product that does not appear on its component's Element;
- a recommendation that is the source of no Check and is not listed under
not_applicablewith a reason; - a Check whose
sourceis not a requirement or recommendation, or an Element that realises something that is not a component.
Recommendations marked not applicable are carried in the graph's summary and shown to the user at the design Approval.
The rule checks that each link exists, not that it is right. A vague Check passes here and is caught later as not_verifiable, or by the user at Approval.
Tests: tests/execution/test_requirements_chain.py, "the Requirements chain has no gap", including one through submit_deliverable.