Files
gcp_solution_architecture_a…/.agents/plans/iter-07-change-requests/MAP.md
Jonathan Boniface 5ef434d00e feat: Change requests against a Baseline (ADR-0006)
A caller restates a request to say how requirements have changed, naming a
completed Execution of the same Customer case as the Baseline.

- app/baseline.py reads a Baseline from its files and refuses one that
  does not exist, did not complete or belongs to another case, before
  anything runs or is recorded. A Baseline is never modified.
- Requirements carry a change (unchanged, added, changed, removed) and a
  reason. Submission is refused when a Baseline requirement disappears, an
  id is reused, or an unchanged requirement's text differs. A removed
  requirement stays on record and asks nothing downstream.
- Each Specialist starts from its delivered version; the graph and the code
  are its working copy, and the description is carried over when the
  design's shape is the same.
- app/workflows/changes.py compares versions by id and traces what each
  changed requirement reaches; anything else that changed is listed as
  unrequested. Approvals show the change for their Phase, and changes.json
  is written with the full Deliverables.
- Intake no longer starts a message read as a change: it names the
  Execution to give as the Baseline.
- A fifth evaluation case runs a request and then a change to it, with
  four checks that the change is recorded, reaches Checks, stays contained
  and costs less than its Baseline.

Tested with scripted agents only; no Change request has run with real
models.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 11:38:15 +01:00

2.3 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: steps 1 to 6 and 8 built (2026-10-09), covered by the deterministic suite; no Change request has run with real models. Step 7's evaluation case and checks are built and its run is outstanding 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. Accepted 2026-10-07.
  • 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 built; not run with real models
3 Requirements revised with a change record M built; not run with real models
4 Later Specialists revise from the Baseline M built; not run with real models
5 Approvals show the change S built; not run with real models
6 Change summary and version line in the case S built; not run with real models
7 Evaluation: a change case M case and checks built; run outstanding
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