[HARDENING] PENDING-179 AMENDMENT 2: the [FIX] warrant is void at every site

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

PENDING.md

@@ -3676,6 +3676,8 @@ So **PENDING-138 and this entry are worded to avoid the bare uppercase token**,
 > ⚠ **This is OWED-1's wrong-subject family seen from underneath, and it does not duplicate it.** OWED-1 asks whether the control's *subject* is the claim's subject. This asks whether the control had any *cases* at all — a control can have the right subject and still be vacuous. The two fail independently and the cheap one is checkable by machine.
 >
 > ⚠ **The rule generalizes past this instance, which is why it is queued rather than patched in place:** it applies to every must-detect in the fleet, and turning it on will convert some currently-green controls to red. That is the point, and it is also why it is a ruling rather than an edit.
+>
+> ⚠ **LIMITATION, added 2026-09-04 — this rule catches ONE of two vacuity classes, and not the one that produced the week's worst instance.** The `wake-digest.py` selftest control whose failure began this whole thread had **thirteen files in its denominator**: it passes this rule and still tests nothing about its subject, because its predicate (`"wrapped" in _v`) does not implement the subject its label names (*"a real session"*). **Empty-set vacuity is what this entry catches; wrong-subject vacuity with a full set belongs to OWED-1 and is invisible here.** Do not read a fleet-wide denominator sweep as having established that the controls test what they claim.
 
 ---
 ## PENDING-142 — The open/closed criterion answers "does a REVIEWED header name this id?", not "is this item still awaiting the steward"
@@ -6982,3 +6984,38 @@ That is a separate decidable unit; merging it here would reproduce the CLASS E d
 **6. Unbundle the two acts; the suspension goes first.** The parent's resumption order is (1) `git init`, (2) suspend. But the parent's own *decisions deferred* records the `git init` as a **steward call** — 144 MB, full transcripts, a remote question — so it may wait days. **The suspension is the act with a firing distance: N=65 against 84, 19 away, 13 net in the last measured three days.** The two touch different files and neither depends on the other; serializing them **puts the deadline behind the deliberation.** The docstring stays false in the meantime, **which is the correct state for a docstring describing a thing that is not true yet.**
 
 **Awaiting:** Steward authorization, jointly with PENDING-178. ⚠ **Point 5 is a condition on an act already directed, not a new proposal** — if the suspension proceeds without a replacement bound, REVIEWED-123 condition 2 is defeated by the act meant to protect its trial.
+
+### AMENDMENT 2 — 2026-09-04 — the `[FIX]` warrant is void at every site, and the date question is retired by finding
+
+**1. THE `[FIX]` WARRANT IS WITHDRAWN. Nothing in the census is currently `[FIX]`-warranted.**
+
+Traced rather than accepted. The 2026-09-03 reclassification rested on exactly 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.* Verified at source, the predicate is:
+
+```
+_v = [wrap_verdict(transcript_span(p), _ev)[0] for p in _tx[-14:-1]]
+chk(f"a real session reads as WRAPPED end-to-end  [{_v.count('wrapped')} of {len(_v)}]",
+    "wrapped" in _v)
+```
+
+**`"wrapped" in _v` does not restrict to real sessions anywhere.** So restoring real sessions to the slice **repairs nothing**: the test still passes on mumbles alone, and it 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 no change to what enters the slice reconciles them.
+
+- **Sites 2 and 4** (`previous_transcript`, `newest_transcript`) never had a quoted specification to be repaired against.
+- **Site 3** had one, and its own implementation contradicts it.
+- **Site 1** is excluded on receipt and untouched.
+
+⚠ **Withdrawn explicitly rather than left to be superseded**, because *"sites 2–4 are `[FIX]`, merely gated"* is precisely the premise a later session inherits without re-deriving. The 2026-09-03 handover's acceptance of the reclassification is withdrawn by its author; the archived Active Session block carrying it (`MEMORY-reference.md`) is annotated in place rather than edited, since it is a verbatim record of what was believed then.
+
+**Consequence for the joint ruling:** whatever replaces the selftest is **a rewrite of the predicate against its label** — a larger act than the one that was reclassified, and not available under any `[FIX]` reading.
+
+**2. THE DATE QUESTION IS RETIRED BY FINDING, not open.** AMENDMENT 1 point 4 recorded it as open; that is now withdrawn. The date was wanted to test one inference — *if the first failing run predates 2026-08-25, the mumble is not its only cause.* **The predicate finding settles that without the date.** A test asking whether *any* transcript wrapped has never tested its label, and has not done so **since it was written** — necessarily predating the mumbles. **The mumble is not its cause at all**, nor even a contributing one; it only changed what fills a slice whose composition the test was already ignoring. ⚠ **Recorded as RETIRED so the next session does not spend a morning replaying `wrap_events()` git history for an answer that no longer discriminates.** What the intermittency tracks is total wrap-verdict density — nothing in thirteen wrapped — which is a fact about wrap behaviour and **evidence about nothing in -178 or -179**.
+
+**3. TWO VACUITY CLASSES, AND OWED-5 SEES ONLY ONE.** The selftest had **thirteen files in its denominator**. It passes the denominator rule and tests nothing about its subject regardless.
+
+| class | shape | caught by |
+|---|---|---|
+| **empty-set vacuity** | the control has no cases | **OWED-5** |
+| **wrong-subject vacuity** | full denominator, predicate does not implement the label's subject | **OWED-1's family — not OWED-5** |
+
+⚠ **Stated so OWED-5 is not over-trusted on the strength of having been earned the same week.** The wrap's open question — *how many fleet controls have a denominator of zero* — is worth running and now has a **harder, more common sibling: how many controls have a predicate that does not implement the subject named in their own label.** The selftest is the demonstrated instance, which makes this a **recurrence of OWED-1 rather than a discovery**.
+
+**Awaiting:** Steward authorization, jointly with PENDING-178. ⚠ **Three of this item's four load-bearing claims have now been corrected by the jurist or by re-measurement within 24 hours of filing.** That is the configuration working, and it is also a reason to read the remaining claims as provisional rather than settled.