[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
2026-09-04 10:59:31 +02:00
parent 9fba331e3e
commit 324cf77023
6 changed files with 145 additions and 8 deletions
@@ -295,3 +295,72 @@ The vacuous `0/0` was caught by a **standing rule** (*a null search is evidence
 not by luck — the class was instrumented. Declining to edit the false docstring, with the reason
 given. And OWED-5's posture: a rule resting on one observed instance, carrying a stated test that
 could retire it as an accident.
+
+---
+
+## ADDENDUM 2 — the `[FIX]` warrant is void, the date question is retired, and OWED-5 is narrower than it looked
+
+⚠ **Second jurist pass, same day.** Three corrections; the first changes what the joint ruling must cover. Filed as `PENDING-179 AMENDMENT 2`.
+
+### The `[FIX]` warrant is void at every site — traced, not accepted
+
+The 2026-09-03 reclassification rested on one argument: *the label says "a real session reads as
+WRAPPED end-to-end", the sample contains no real sessions, so restoring the population repairs the
+instrument against its existing specification.* Read at source:
+
+```
+_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.** 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.** Label and test disagree about
+*subject*; 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. **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 reclassified.
+
+⚠ **Withdrawn explicitly in three places** (this record, `MEMORY-reference.md`'s archived block by
+annotation-not-edit, and the 09-03 session record) because *"sites 2–4 are `[FIX]`, merely gated"* is
+exactly the premise a later session inherits without re-deriving.
+
+### The date question is RETIRED BY FINDING — AMENDMENT 1 recorded it open; that is withdrawn
+
+It was wanted to test one inference: *a start predating 2026-08-25 would mean the mumble is not the
+only cause.* The predicate finding settles it **without the date** — a test asking whether *any*
+transcript wrapped has never tested its label **since it was written**, necessarily predating
+mumbles. **The mumble is not its cause at all**, only a change in what fills a slice whose
+composition the test was already ignoring. ⚠ **Do not replay `wrap_events()` git history for it.**
+What the intermittency tracks is total wrap-verdict density — evidence about nothing in -178 or -179.
+
+### OWED-5 sees one of two vacuity classes
+
+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 | no cases at all | **OWED-5** |
+| wrong-subject vacuity | full denominator, predicate ≠ label's subject | **OWED-1 — invisible to OWED-5** |
+
+⚠ The fleet denominator sweep has a **harder and 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, making this a **recurrence of OWED-1, not a discovery**.
+
+### On the correction pattern itself — worth banking for PENDING-89
+
+**Three of PENDING-179's four load-bearing claims were corrected within 24 hours of filing**, by the
+jurist or by re-measurement. That is the configuration working. It is also a reason to read the
+remaining claims as provisional.
+
+⚠ **And one correlated miss, which is PENDING-89's actual question.** The jurist declined credit for
+self-correcting on urgency, noting the correction only ran because a measured N of 65 arrived, and
+that the error was a *class* error — reading the absence of a stated rate as the absence of urgency.
+**The executor shared that miss.** Both items correctly withheld a rate; both parties read the
+withholding as slack; neither flagged the firing distance until a number was measured. **What one
+missed, the other missed too, in the same direction, for the same reason.** Recorded per
+Constitutional Constraint 6, which requires evidence against the differently-biased-checkers doctrine
+to be logged when observed rather than only when sought.