Files
gcp_solution_architecture_a…/.agents/plans/iter-06-target-architecture-graph/steps/step-7.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

856 B

Step 7 — Implementation Detail

  1. render_mermaid draws a left-to-right flowchart with every Element (name and product) and every Relationship (its kind) exactly once. Node ids are generated, and characters Mermaid reserves are stripped from labels, so any graph step 3 accepts renders.
  2. submit_deliverable adds architecture.mmd to the Target architecture's attachments when it accepts the submission. No Specialist draws it.
  3. Removed: the architecture_diagram Deliverable, agents/diagrammer.md and its bundle entries.
  4. /generate keeps its mermaid_diagram key, now read from the Target architecture. The packager is told to embed that attachment unchanged.

The local mermaid_check tool stays in the bundle; the evaluation still uses it.

Tests: tests/execution/test_requirements_chain.py, "the diagram is a view of the graph".