Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2716

A case derives its budgets and lists from what it tests, never pins them

Where it stands

devtask.issue
Readiness
in_progress execution began; the record carries started_at
Status
ACTIVE
Can start
not now
Milestone
Milestone status
ACTIVE
Wave
0
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
0 of 1
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2716

majordomus plan verify I2716

majordomus plan done I2716

What it is

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).
Now
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.
Wanted
A lint over test/cases reports a literal budget, count or size compared against a product's output without a comment giving its margin, and the release-record-cases list is generated from the cases that name a release-record path (or checked against them by a structure gate, not only by case 94).
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • Adding a case that names the release record without listing it fails a structure gate, not only case 94
  • A hand-pinned budget in a case without a stated margin is reported
Validation
bin/majordomus plan validate
Evidence required
pinned_values_are_reported_case
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
scripts/liveness-check.ai/repo/ci/gates.yamltest/cases
Not
unknown: the record declares no `non_scope`
Depends on
none
Priority
p2
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-14
Updated
2026-10-14T22:50:08Z
Started
2026-10-14T22:50:08Z
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

LevelCodeMessageReproduce
WARNscope_conflictshares test/cases with I2717; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2718; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2720; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2723; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2731; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2734; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2740; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2742; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2747; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2760; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares test/cases with I2786; they may not run concurrentlymajordomus plan validate