feat: establish the Target architecture as a graph before code
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>
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
# Step 11 — Implementation Detail
|
||||
|
||||
Partly done. The checks are built; the evaluation run that this step exists for has not been made.
|
||||
|
||||
Built in `eval/scoring.py`:
|
||||
|
||||
- `requirements_chain_complete`: the delivered data files form a chain with no gap.
|
||||
- `every_check_passes`: validation ended with no Check failed or not verifiable, and the dry-run not failed.
|
||||
- `diagram_matches_graph`: the delivered diagram is exactly the rendering of the delivered graph.
|
||||
|
||||
These replaced `components_trace_to_requirements` and `no_blocking_findings` from iteration 4 step 8.
|
||||
|
||||
Outstanding, and why:
|
||||
|
||||
- **No evaluation run.** The owner stopped the last run on 2026-10-06 and asked that no further cases start until they advise. Nothing in this iteration has run against a real model.
|
||||
- **The acceptance criteria are therefore unmet:** all cases scoring at least 0.8, the failing-Check set never growing between passes, and at most one Revision of the deployment guidance in two of three cases.
|
||||
- **Not built:** the per-case record of validation passes and the Check ids failing at each. The evaluation reads only the final verdicts today.
|
||||
- **Thresholds** from iteration 4 step 8 are still unset.
|
||||
|
||||
Do not mark this step complete until a run meets the criteria. (`legacy-baseline` was removed on 2026-10-07 on the owner's instruction, ahead of this.)
|
||||
Reference in New Issue
Block a user