Files
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.9 KiB

Plan Map

Iteration: 2, solution architect agent Intent: Replace the linear template pipeline with a portable, hierarchical ReAct agent that runs the upstream google-cloud-solution-architecture Skill's workflow. An Orchestrator reasons over a code-declared dependency graph of Deliverables and delegates to one Specialist per Deliverable. Behaviour lives in Agent Skills; the Cloud provider is configuration. Branch: feat/solution-architect-agent This directory covers: steps 1 to 9, the spec's build increments 1 to 9

Sources of truth

  • .scratch/solution-architect-agent/spec.md: the design, the decisions table, the acceptance list, and a dated ## Comments entry per finished increment. Its module paths predate iteration 3; translate them with the table in ../README.md.
  • docs/adr/0002-skills-are-the-portable-unit-of-behaviour.md and docs/adr/0003-langgraph-holds-state-adk-agents-reason.md: the two decisions every step serves.
  • CONTEXT.md: the glossary. Use its terms.

Status

Step Increment Status Commit
1 Environment and baseline complete 0851171
2 Vendored Skills and provider bundle complete 2976dfa
3 Deliverables and Ledger complete c841094
4 Execution graph complete d9214c6
5 ADK runtime and role files complete f040493
6 Tools and remote MCP servers complete ed104e5
7 Interfaces (A2A, /generate) complete ad371b2
8 Evaluation complete 7ee49ab
9 Cleanup done in iteration 3 none

Dependency graph

  • Step 1: no dependencies
  • Step 2: depends on step 1
  • Step 3: depends on step 1
  • Step 4: depends on step 3
  • Step 5: depends on step 2, step 4
  • Step 6: depends on step 2, step 5
  • Step 7: depends on step 4, step 5, step 6
  • Step 8: depends on step 7
  • Step 9: depends on step 8 passing its threshold