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>
764 B
764 B
Step 3 — Implementation Detail
app/workflows/target_architecture.py, pure and without I/O:Element,Relationship,Check,NotApplicable,TargetArchitecture, andparse_graph, which returns the graph or raisesGraphErrorlisting every fault.- The file is
target-architecture.jsonwithelements,relationships,checksand optionalnot_applicable. - Refused, with the id named: a repeated id; a Relationship whose
fromortois not an Element; a Check that applies to nothing in the graph; an Element with no Check; a missing or empty field. - An Element's
componentis optional, for supporting Elements such as identities, keys and networks.
Tests: tests/execution/test_requirements_chain.py, "the graph is well-formed".