I3383 — 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

✕BLOCKED wave 2 · p1 · docs profile · parallel safe

Part of delivery-economics-are-measured-over-declared-windows — Delivery economics are measured on corpus runs and on real work over a window registered before it opens, and published with their denominators and losses.

Objective

Register the T3 window protocol in .ai/repo/benchmarks/proof-plan.yaml: a period that begins after the registration's commit, the work it admits (every task started in the period in any checkout of this repository), accepted as I0401 defines it, the bound per field on its not-observed share, the snapshot of checkouts taken at open and close, and the cross-check against tracked session records. Record which fields are expected to read not observed in light of I3373's decisions.

Why

T3 of the owner's report of 2026-10-19 asks for real figures. The critique found an instrument without a measurement over work chosen in advance does not answer T3, and that removed worktrees bias the denominator, so the checkout snapshot and the session-record cross-check are part of the protocol.

Current state

No window is declared. git ls-files .ai/repo/sessions counts 91 tracked session records; policy.yaml:122-123 sets commit_record_on_end and push_record_on_end.

Desired state

The T3 protocol validates with its digest and the T3 row reads running once the period opens.

Scope

• .ai/repo/benchmarks

Out of scope

• Measuring the window (I3384)
• Changing what the session lifecycle commits

Dependencies

• I3352✕BLOCKED The six proof tests are registered, each with the claim it settles and its instrument, and none carries a protocol yet
• I3373○READY The program's blocked dependencies are cut or re-scoped by recorded owner decisions, or recorded as refused with the criteria they leave outside the window

What waits on this

• I3384✕BLOCKED 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

Acceptance criteria

• The protocol validates, and its period starts after its registration commit
• Each field has a declared not-observed bound
• The protocol names the snapshot and the cross-check

Validation

• majordomus economics proof
• cargo test --manifest-path apps/majordomus-cli/Cargo.toml --test economics
• majordomus plan validate

Evidence required

• t3_window_registered

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/I3383.yaml. Read it back with majordomus plan show I3383.