Files
gcp_solution_architecture_a…/.agents/plans/iter-07-change-requests/MAP.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

2.1 KiB

Plan Map

Iteration: 7, Change requests Intent: Let a user restate a request to say how their requirements have changed, at a high level, and receive the delivered architecture updated from where it stood, with an account of what changed and why. Status: planned. ADR-0006 was accepted on 2026-10-07 and the glossary updated (step 1). Build after iteration 6 step 11 has a passing evaluation run This directory covers: steps 1 to 8

Sources of truth

  • docs/adr/0006-a-change-request-starts-from-a-baseline-execution.md: the decision and its four points to confirm. Status proposed.
  • docs/adr/0005-the-target-architecture-is-an-explicit-graph.md and ../iter-06-target-architecture-graph/: the ids along the Requirements chain that a change is traced through. Build iteration 6 first.
  • CONTEXT.md: today it says an Execution starts clean and a Customer case never feeds one Execution into another. Step 1 changes those entries; until then they stand.
  • iter-04-learning-and-skills/steps/step-15.md: the Customer case layout, execution.json and the Intent history (intent/history.json) that a Baseline is found through. A Change request is the next statement in that history.

Status

Step What Size Status
1 Accept ADR-0006 and update the glossary S complete: accepted 2026-10-07
2 Start an Execution against a Baseline M planned
3 Requirements revised with a change record M planned
4 Later Specialists revise from the Baseline M planned
5 Approvals show the change S planned
6 Change summary and version line in the case S planned
7 Evaluation: a change case M planned
8 Remove the legacy-baseline case S complete: removed early on the owner's instruction, 2026-10-07

Dependency graph

  • Step 1: no dependencies
  • Step 2: depends on step 1, iteration 4 step 15
  • Step 3: depends on step 2, iteration 6 step 2
  • Step 4: depends on step 3, iteration 6 steps 4 and 8
  • Step 5: depends on step 4, iteration 6 step 6
  • Step 6: depends on step 4
  • Step 7: depends on step 5, step 6, iteration 6 step 11
  • Step 8: no longer gated; done on 2026-10-07