Traced rather than accepted. The 2026-09-03 reclassification rested on one
argument: the control's label says "a real session reads as WRAPPED
end-to-end", its sample contains no real sessions, therefore restoring the
population repairs it against its existing specification.
Read at source, the predicate is `"wrapped" in _v`. It does not restrict to
real sessions anywhere. Restoring the population repairs nothing: the test
passes on mumbles alone, and would pass on a correctly-populated slice in
which every real session failed. The defect was never the sample — the label
and the test disagree about their subject, and nothing that changes what
enters the slice reconciles them.
Sites 2 and 4 never had a quoted specification. Site 3's is contradicted by
its own implementation. Site 1 is excluded on receipt. Nothing in the census
is [FIX]-warranted, and whatever replaces the selftest is a rewrite of the
predicate against its label — larger than the act that was reclassified.
Withdrawn explicitly in three places rather than left to be superseded:
"sites 2-4 are [FIX], merely gated" is precisely the premise a later session
inherits without re-deriving. The archived Active Session block carrying it
is annotated in place, not edited — it is a verbatim record of what was
believed then.
Also:
- the selftest date question is RETIRED BY FINDING, not open. AMENDMENT 1
recorded it open; withdrawn. A test asking whether any transcript wrapped
has never tested its label since it was written, necessarily predating
mumbles, so the mumble is not its cause at all. Do not replay
wrap_events() git history for an answer that no longer discriminates.
- OWED-5 annotated: it catches empty-set vacuity only. The selftest had 13
files in its denominator and tested nothing about its subject regardless.
Wrong-subject vacuity is OWED-1's class and invisible to OWED-5.
- logged for PENDING-89: jurist and executor shared one miss in the same
direction — both read the absence of a stated rate as the absence of
urgency, and neither flagged the firing distance until N was measured.
MEMORY.md hit 314 bytes of headroom while carrying this and was condensed to
pointers after verifying every claim had a home in the item and the session
record. 22,263 bytes, 2,723 headroom.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
Five corrections from the jurist on the wrap, two operational, plus one new
measurement that supersedes this session's own origin claim.
The correction that matters: the wrap credited the handover's ordering "at
every point it was load-bearing". The gate's POSITION held; its CONTENT did
not. Gate 2a as specified was one arm, one transcript, expected 0 — run as
written it greens, because 22 of 24 mumbles return 0. The finding exists
because the specification was replaced with independent whole-population
ground truth plus an unrequested must-not-flag arm. "Follow the handover" is
the wrong lesson and the more comfortable one.
New, and it supersedes the 2026-09-03 origin record: the failing selftest
control does not test the claim on its label. Measured live on the actual
_tx[-14:-1] slice — 1 real session, 12 mumbles, and verdict `wrapped` comes
from 1 real session and 4 MUMBLES. The predicate `"wrapped" in _v` is
satisfiable by mumbles alone, so it would pass with zero real sessions in
the slice. OWED-1's wrong-subject family, inside the control that was meant
to be evidence about mumbles.
Still open, and recorded as open rather than reframed again: the date of the
control's first failing run. The archive reconstruction is not sound for it.
Operational for the next session:
- unbundle the two acts, suspension first; the git init is a steward call
and may wait, while the suspension has a firing distance (65/84)
- the suspension MUST carry a replacement bound in the same act —
REVIEWED-123 cond. 2's bound IS grading at 84, and suspending grading
removes exactly that bound
Also: gate 2c's narrowing limitation moved into the item, since the item is
what gets ruled on.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
Session record, ledger merge, MEMORY.md rotation (prior Active Session
demoted verbatim to MEMORY-reference.md), 6 KG triples, and OWED-5 queued
in PENDING-141's ratified owed-entries list.
OWED-5: a must-detect control must report its denominator, and a denominator
of zero is a FAIL. Steward-stated 2026-09-04, queued unruled — the ladder is
frozen under REVIEWED-123, and turning the rule on converts currently-green
controls to red across the fleet, which is a ruling rather than an edit.
Earned on the vacuous PASS (0/0) that nearly certified a broken discriminator.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
