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.4 KiB
1.4 KiB
Step 6 — Implementation Detail
PhaseIdhas five members.solution_architectureis now the design Phase (product selection, design recommendations, Target architecture). The newsolution_implementationholds the architecture description and the deployment guidance. The idsolution_architecturewas kept so recorded Executions and callers do not break.- The Ledger's existing rule does the gating: a Dependency across Phases is met only on Approval, so nothing in implementation is ready until design is approved.
- The design Approval carries a summary of the graph (counts of Elements, Relationships and Checks, and recommendations treated as not applicable).
describe_promptinapp/presentation.pystates that no code is written until it is approved. workflow.yamllists the five Phases; its test checks it against the dependency graph. The A2A card derives from the graph and needed no change.
Revision behaviour that follows: reopening the deployment guidance withdraws the implementation and validation Approvals and leaves the design approved; reopening the Target architecture withdraws design, implementation and validation, and the code cannot restart until the design is approved again.
Tests: tests/execution/test_ledger.py, test_the_user_approves_the_graph_before_any_code_is_written in tests/execution/test_requirements_chain.py, tests/execution/test_presentation.py.