I3384 — The first delivery window is measured at its close and published with its denominators, the work not accepted and the checkouts it could not read
At the window's close, run economics tasks over the period, write the T3 trial record with per field the count, median, denominator and not-observed count, every task not accepted, every checkout of the snapshots whose ledger could not be read, and the task count against the tracked session records; commit it under .ai/repo/benchmarks/trials/t3-delivery-economics/, add the window tests, regenerate the economics projections and let the T3 row compute its status.
BLOCKED wave 5 · p1 · implementation profile · parallel safe
Blocked. This issue cannot start until I3383, I3377, I3378, I3381, I3354, I3356 are done. The status is derived from that, not declared.
Objective
At the window's close, run economics tasks over the period, write the T3 trial record with per field the count, median, denominator and not-observed count, every task not accepted, every checkout of the snapshots whose ledger could not be read, and the task count against the tracked session records; commit it under .ai/repo/benchmarks/trials/t3-delivery-economics/, add the window tests, regenerate the economics projections and let the T3 row compute its status.
Why
T3 of the owner's report of 2026-10-19 asks for the real delivery economics, losses included. If I3379 or I3380 has not landed by the close, those fields read not observed and the row fails its bound, which is published as such rather than delaying the window.
Current state
No window record exists.
Desired state
A committed T3 record and a computed T3 row.
Scope
- .ai/repo/benchmarks
- apps/majordomus-cli/tests/economics.rs
- docs/generated/economics.json
- docs/generated/economics.md
- docs/generated/economics.yaml
- site/data/generated/economics.json
Out of scope
- Extending the window after it opens
- Excluding a task to improve a field
Dependencies
- I3383BLOCKED The T3 delivery window is registered before it opens: its period, the work it admits, the definition of accepted and a bound on each field's not-observed share
- I3377BLOCKED A task's prompt records, restarts and manual changes are counted by type from the records that already hold them, each with the ids behind it
- I3378BLOCKED A permission request the provider reports leaves a receipt with its own elapsed time, and economics.tasks counts it as an approval
- I3381BLOCKED A task counts as accepted only by the written definition of an accepted outcome, with the issue's furthest delivery stage shown beside it
- 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
- I3356BLOCKED The site's economics page publishes the scorecard from the generated summary, failed and inconclusive tests and every loss in the same rows as passed ones, each linking its records
Acceptance criteria
- The record passes the loader with the T3 digest
- Every field states its denominator and not-observed count
- Every unread checkout is named
- The task count is reconciled with the tracked session records, and any difference is listed
- A test fails on a fixture record that drops a not-accepted task
Validation
- cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test economics
- majordomus economics tasks
- majordomus economics proof
- majordomus generate --check
Evidence required
- t3_window_record_committed
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/I3384.yaml. Read it back with majordomus plan show I3384.