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:
2026-10-09 13:50:18 +01:00
parent 5ef434d00e
commit 59a641fded
6 changed files with 89 additions and 11 deletions

View File

@@ -220,3 +220,16 @@ To verify the batched schema lookup (iteration 4 step 18) and the corrected conf
This is the first run of case 04 at 100%.
## Runs of 2026-10-09, 10:38 UTC (`eval/results/20261009T103822Z/` and `...103827Z/`)
A regression check after Change requests (iteration 7) changed what every Specialist is told. All pass with no warnings.
| Case | Score | Time | Tokens | Revisions |
|---|---|---|---|---|
| 02 | 1.00 | 31 min | 3.93 M | 1 |
| 03 | 1.00 | 22 min | 2.32 M | 1 |
| 04 | 1.00 (12 of 12) | 40 min | 3.20 M | 1 |
| 05, the request that the change case then changes (case 01's) | completed | 36 min | 4.32 M | 1 |
Case 03 was its fastest and cheapest yet. The change case itself is recorded in `../../iter-07-change-requests/steps/step-7.md`.