Repository navigation
docs(OMN-15535): OCC DoD contracts + receipts for 3 proof-satisfied steel tickets (OMN-15535, OMN-15490, OMN-15493) - #5754
jonahgabriel wants to merge 2 commits into
Conversation
…tisfied false-Backlog steel tickets (OMN-15535, OMN-15490, OMN-15493)
Authors contracts/OMN-{15535,15490,15493}.yaml plus 13 PASS receipts under
drift/dod_receipts/, so the dod_verify path has a receipt surface for three
OMN-15154 cluster tickets whose fixes are already merged on
jonahgabriel/steel_onslaught main while their Linear tickets carry a single
Backlog stateHistory entry. Same class and same shape as OCC #5544 (7 wave-1
tickets, merged 5f58e71); these three post-date that batch.
No Linear status is changed here. Per doctrine a Done flip routes only through
dod_verify with durable evidence.
Per-ticket binding (each contract pins its OWN merged PR + merge SHA):
OMN-15535 -> steel#239 @4bae73ea51a4f3d42d24ccdcaf68d9ab61d1a9a5
OMN-15493 -> steel#236 @d2a5d9aaeddbf71039d34820bb568e5c9d4561be
OMN-15490 -> steel#237 @e3dbd0171709d9cdd9fb80c4df6b85688a398803
13 checks, all hosted-runnable and pinned to immutable merge SHAs (never a
feature-branch ref, never a workflow-run conclusion). Executed GREEN as
written on the gate host, then RED-proven by repointing every pinned SHA at
its merge commit's first parent: 13/13 flipped RED.
Author is not the implementer: the fixes were built by the authorized-wave-0730
and fable-night-0730 steel lanes; this contract package is authored by
fable-ws0-0731/laneB2 (no-self-authored-evidence rule).
Honest scope note (OMN-15493): the negative leg is scoped to executed `run:`
lines rather than the whole workflow file, because the literal string
`-m "unit or integration"` survives at ci.yml:45 inside the comment documenting
the defect. A whole-file absence assertion would be permanently RED against
correct code.
Cites OMN-15535, OMN-15490, OMN-15493.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 35 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (19)
Comment |
…ts for all three cited tickets occ-preflight/eligibility resolves the tickets a PR owns from the title tokens when the body carries no closing keyword, so this PR owns OMN-15535, OMN-15490 and OMN-15493 and each needs a PASS receipt bound to PR #5754. Appends the standard occ-self-bind item + receipt to each contract, mirroring occ-self-bind-pr-5544 and occ-self-bind-pr-5752. Append-only: every pre-existing dod_evidence entry is byte-intact; the new item is added after the last one in each file, and all 13 original receipts still hash-match their contract entries (per-entry hashing, OMN-13888). Scope disclosure, recorded in each item description: this is a BINDING STAMP, not substantive proof. It flips no Linear status. Cites OMN-15535, OMN-15490, OMN-15493.
|
Superseded by #5756. This PR carried the identical package but on a single-ticket branch ( |
What this is
Net-new OCC receipt surface for three false-Backlog steel tickets whose fixes are already merged on
jonahgabriel/steel_onslaughtmain. Each Linear ticket still carries a singleBacklogstateHistory entry — receipt debt, not unbuilt work. Same class and same shape as OCC #5544 (5f58e711, 7 wave-1 tickets); all three of these were created after that batch, so they were never covered.No Linear status is changed by this PR. A Done flip routes only through
dod_verifywith durable evidence; this PR is the durable evidence it currently cannot find (CONTRACT_MISSINGon all three).Files (net-new only, 16)
contracts/OMN-15535.yaml,contracts/OMN-15490.yaml,contracts/OMN-15493.yamldrift/dod_receipts/OMN-15535/,.../OMN-15490/,.../OMN-15493/Nothing existing is edited. No receipt or contract already on
devis touched.Per-ticket binding
4bae73ea51a4f3d42d24ccdcaf68d9ab61d1a9a5d2a5d9aaeddbf71039d34820bb568e5c9d4561bee3dbd0171709d9cdd9fb80c4df6b85688a398803The three merges are a single chain on steel
main:4bae73ea→d2a5d9aa→e3dbd017.Falsifiability
13 checks, every one hosted-runnable and pinned to an immutable merge SHA — never a feature-branch ref (OMN-15540 Rule F / F2), never a workflow-run
.conclusion(Rule F1).stickybeatz-studioat authoring time.The discriminating legs are deliberately negative where a positive grep would be vacuous:
.model_copy(across the five reducer modules +match/fold.py+match/state.py. Grepping forevolvealone would pass on a tree that addedevolvewhile leaving the bypass — the exists-but-wrong shape the ticket filed.stdout=completed.stdout,and not a[-2000:]-sliced variant — the discriminator between "the message reads nicely" and "the persisted record retains the diagnosis".run:line carriesunit or integrationand exactly one pytest invocation exists in the workflow.Honest scope note (OMN-15493)
The negative leg is scoped to executed
run:lines rather than the whole file: the literal string-m "unit or integration"survives atci.yml:45inside the comment documenting the defect being fixed. A whole-file absence assertion was written first, measured RED against correct code, and narrowed. Recorded here rather than silently dropped.No self-authored evidence
The implementers were the steel build lanes (
authorized-wave-0730/*,fable-night-0730). This package is authored byfable-ws0-0731/laneB2, which built none of the three fixes.Evidence trail
Lane B (
fable-ws0-0731/laneB) posted the read-only proof-debt re-reads that scoped this work; each contract's checks were derived from live readback atorigin/main, not from those comments:5983d40cand116913ccb40dee60bf1ad84dPeer session
fable-steel-0731independently reached the same terminal state on OMN-15490 (bedf003f, corrected by39988ed6) and OMN-15493 (8c17b496, corrected byf1507a40): merge evidence real,dod_verifyblocked onCONTRACT_MISSING, path to Done = a contract authored by a non-implementer. That is this PR.Cites OMN-15535, OMN-15490, OMN-15493.
Evidence-Ticket: OMN-15490
Evidence-Ticket: OMN-15493
Evidence-Ticket: OMN-15535
Evidence-Source: OCC#5755