fix: a changed functional requirement is reached through its components
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>
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
**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
|
||||
**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
|
||||
@@ -17,12 +17,12 @@
|
||||
| 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 |
|
||||
| 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
|
||||
|
||||
Reference in New Issue
Block a user