The change-case check asked for a changed Check whose source is the changed requirement. A functional requirement is carried by the components that serve it, so it is reached through a Check on an Element realising one. Plans record the first Change request with real models: a retention change made in 18 minutes for a third of its Baseline's tokens, touching seven Checks on one Element and nothing else, and the regression runs of cases 02, 03 and 04, all at 100%. Iteration 7 is complete. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
38 lines
2.3 KiB
Markdown
38 lines
2.3 KiB
Markdown
# 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:** complete (2026-10-09). The change case ran with real models: a retention change was made in 18 minutes for a third of its Baseline's tokens, touching seven Checks on one Element and nothing else (`steps/step-7.md`)
|
|
**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 | complete |
|
|
| 3 | Requirements revised with a change record | M | complete |
|
|
| 4 | Later Specialists revise from the Baseline | M | complete |
|
|
| 5 | Approvals show the change | S | complete |
|
|
| 6 | Change summary and version line in the case | S | complete |
|
|
| 7 | Evaluation: a change case | M | complete: one run, all change checks pass |
|
|
| 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
|