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

958 B

Step 4 — Implementation Detail

  1. DeliverableKind.TARGET_ARCHITECTURE, in the design Phase, depending on product selection and design recommendations. Its content needs Elements, Relationships and Checks sections; its attachment is the graph.
  2. Role file agents/target-architect.md. In the bundle it loads the solution-architecture and requirements-chain Skills, reaches the documentation MCP server, and runs on the Pro model tier.
  3. skills/requirements-chain/SKILL.md gives the graph's format and how to write a Check that can be verified from code, with verifiable and non-verifiable examples.
  4. The role file states that implementation detail is the agent's job and the user stays at the level of Intent.

Not verified: no real model has produced a Target architecture yet. Whether one can write Checks specific enough to verify, in one run and inside its tool budget, is the main risk of this iteration and is what step 11 measures.