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>
765 B
765 B
Step 8 — Implementation Detail
- The deployment guidance depends on the Target architecture and requires
implementation.json: for each Check, the attached file and resource address that satisfies it. - Refused: a Check not accounted for, an id that is not a Check, an entry naming a file that is not attached.
agents/iac-author.mdnow says to implement the Target architecture and nothing it does not ask for, and on a Revision to change only what the failed Checks need.
Changed from the plan: the IaC author's context still carries every earlier Deliverable in full, prose recommendations included, because inputs_of is unchanged. Narrowing it to the graph is iteration 4 step 13.
Tests: test_deployment_guidance_must_account_for_every_check.