I2716 — A case derives its budgets and lists from what it tests, never pins them
Keep a case from failing because its subject grew: a budget, a count or a list of names that a case states by hand is derived from the model or carries the margin and the reason it holds.
DONE wave 0 · p2 · implementation profile · parallel safe
Part of M004 — Performance is executable evidence, and the hot path does no canonical work twice.
Objective
Keep a case from failing because its subject grew: a budget, a count or a list of names that a case states by hand is derived from the model or carries the margin and the reason it holds.
Why
2026-10-14: master 2d226f0836 went red in suite-shard (2) because case 130 compared three surfaces at a hand-pinned 4000-token budget and a fresh init's governance tier grew to 4023 when #1143 added 235 bytes to the seeded scope; the same day case 94 failed a branch because the release-record-cases gate lists its cases by hand and a new case named the release record. Both were fixed by hand in #1145 (budget 16000 with a comment; case 3021 added to the list).
Current state
Cases pin numbers and lists freely; a gate's hand list (release-record-cases) and a case's literal budget are found only when they break.
Desired state
The release-record-cases list is checked against the cases that name a release-record path by a structure gate (scripts/ci/release-record-cases-check), not only by case 94. Reporting a hand-pinned budget without a stated margin moved to I2846 (2026-10-21), so this issue closes on the listing alone.
Scope
- scripts/liveness-check
- .ai/repo/ci/gates.yaml
- test/cases
Out of scope
- Reporting a literal budget, count or size a case compares against a product's output without a comment giving its margin: I2846, split off on 2026-10-21 when this issue's first half was found on master and the second was not.
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- Adding a case that names the release record without listing it fails a structure gate, not only case 94
Validation
- bin/majordomus plan validate
Evidence required
- release_record_listing_case
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| release_record_listing_case | ci | validate run 39438896504 at master 9a5a9b77520: structure job 118758922399 runs scripts/ci/release-record-cases-check (27 cases name the release record, each run by release-record-cases); suite-shard (1) job 118683336189 runs 3033_a_release_record_case_is_listed_by_a_structure_gate (11e53f5a451) | success (the run's only red job is pages, which runs no test) | 573df96 |
Timeline
- started
- 2026-10-14T22:50:08Z
- verified
- 2026-10-20T22:20:19Z
- completed
- 2026-10-20T22:21:05Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2716.yaml. Read it back with majordomus plan show I2716.