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 3 — Implementation Detail
- Working memory. Each Deliverable has a JSON-compatible working memory kept in Execution state (
working, merged by key so parallel Specialists each write their own).ToolFactorynow takes it as a third argument, so tools can remember across attempts. - Pillar advice is remembered under
pillar_advicein the design recommendations' working memory (app/tools/pillars.py). - Semantics of
consult_pillar_advisors: omitpillarsto consult every pillar afresh; namepillarsto re-consult only those, with the remembered advice returned for the rest under a heading marked "(from your earlier consultation)". Failed advice is never remembered. agents/design-advisor.mdtells the design advisor to name only the pillars its feedback touches when revising.
Changed from the plan: the criterion "a changed brief for a pillar invalidates that pillar's stored advice" was not built. The brief is one text for all pillars and a model rewords it on every attempt, so hashing it would discard everything each time. Omitting pillars is the way to refresh all advice.
Tests: tests/execution/test_pillars.py (subset re-consult, full refresh, failed advice not stored, and one through the engine showing advice surviving a Revision).
Not verified: the evaluation run this step calls for. The saving depends on the design advisor following the new instruction; in case 01 it would cut up to 12 of 18 advisor runs.