I3372 — The registered corpus is run in both arms, its records are committed, and its verdict is published with its losses and its origin
With the owner's recorded consent to the ceiling, dry-run the suite, rehearse one pair to confirm a live run records end to end, then run every declared job in the registered order with the pinned release, commit the run records under .ai/repo/benchmarks/economics/runs/corpus, regenerate the economics reports, and publish the T2 verdict whatever it is, stating that the corpus is one synthetic fixture written by the treatment's builders.
BLOCKED wave 6 · p1 · implementation profile · parallel safe
Blocked. This issue cannot start until I3370, I3371, I3354 are done. The status is derived from that, not declared.
Objective
With the owner's recorded consent to the ceiling, dry-run the suite, rehearse one pair to confirm a live run records end to end, then run every declared job in the registered order with the pinned release, commit the run records under .ai/repo/benchmarks/economics/runs/corpus, regenerate the economics reports, and publish the T2 verdict whatever it is, stating that the corpus is one synthetic fixture written by the treatment's builders.
Why
T2 of the owner's report of 2026-10-19 asks for the comparison to be run; no live run has ever been committed. Under ADR 0082 no run is overwritten or dropped and an unfavourable result is shown.
Current state
git ls-files .ai/repo/benchmarks/economics/runs lists only runs/context; branch feature/economics-pilot-runs raised pilot repetitions and committed no run.
Desired state
runs/corpus holds every attempted run; the T2 row reads a computed status with its losses.
Scope
- .ai/repo/benchmarks/economics/runs
- docs/generated/economics.json
- docs/generated/economics.md
- docs/generated/economics.yaml
- site/data/generated/economics.json
Out of scope
- Editing the registration or methodology during the runs
- Re-running or excluding a run to change a verdict
- Changing the calculator; a runner defect becomes its own issue
Dependencies
- I3370BLOCKED The corpus suite is registered and committed before its first run, and the T2 protocol names its registration digest
- I3371BLOCKED Economics summary decides a registered suite's primary outcome by its registered test, reports secondary differences without a verdict word, and refuses typed figures about them
- I3354BLOCKED A pure scorecard function computes each proof test's status, counted sample, effect and losses from committed records, and withholds a verdict until the registered sample is complete
Acceptance criteria
- The consent decision is recorded before the first live session
- economics run --suite corpus --dry-run lists every job in the registered order
- Every declared pair is attempted, and each missing or invalid pair is named with its reason
- Every run within a pair reports the same harness version, model, fixture digest and pinned release
- The published result states the corpus origin
- majordomus economics check and majordomus generate --check pass
Validation
- majordomus economics summary
- majordomus economics proof
- majordomus economics check
- majordomus generate --check
- bash test/run.sh 431_economics_claims_gated
Evidence required
- corpus_run_records
- corpus_verdict_published
- budget_consent_decision
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
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/I3372.yaml. Read it back with majordomus plan show I3372.