Files
gcp_solution_architecture_a…/.agents/plans/iter-04-learning-and-skills/steps/step-4.md
Jonathan Boniface e9246828b3 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>
2026-10-07 13:59:09 +01:00

1.2 KiB

Step 4 — Implementation Detail

  1. DeliverableSpec.contract() returns the sections, attachments and table columns as data; every Specialist's context now carries it as contract.
  2. Role files no longer list required headings. What remains in them is guidance the contract cannot express (what goes under a heading, verdicts, optional headings).
  3. New contracts:
    • technical_decomposition: a Components section and one table whose header names component and requirement.
    • architecture_description: Components and Flow sections. Headings match by suffix, so "Data flow" and "Architecture components" satisfy them.
    • Every required attachment must have content, which gives the diagram's architecture.mmd a minimum bar.
  4. Tests share one contract-complete fixture, sample_submission in app/adk/fake_runtime.py.

Two existing tests used an empty terraform/variables.tf as a fixture; they now use a non-empty one.

Tests: tests/execution/test_deliverables.py, and test_specialist_context_carries_its_contract in tests/execution/test_engine.py.

Not verified with real models: the two new section contracts change what the decomposer and describer must write.