[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.

claude/memory/MEMORY-reference.md

@@ -65,6 +65,9 @@ metadata:
 <!-- demoted from MEMORY.md at the 2026-08-17 wrap -->
 ### Demoted from Active Session at the 2026-09-04 wrap
 
+> ⛔ **SUPERSEDED 2026-09-04 — the `[FIX]` claim in the 2026-09-03 block below is VOID and the block is kept verbatim only as a record of what was believed then.** That reclassification rested on *"the control's label already says 'a real session', so restoring that population repairs it against its own spec."* The predicate is `"wrapped" in _v`, which **does not restrict to real sessions at all** — so restoring the population repairs nothing, and the test would pass on a correctly-populated slice in which every real session failed. **The defect was never the sample.** Sites 2 and 4 never had a quoted specification; site 3's is contradicted by its own implementation. **Nothing in the census is `[FIX]`-warranted.** See PENDING-179 AMENDMENT 2. ⚠ *Annotated rather than edited: the block is a verbatim archive, and "sites 2–4 are `[FIX]`, merely gated" is exactly the premise a later session would inherit without re-deriving.*
+
+
 > 🔴 **NEXT SESSION, FIRST WORK — STEWARD-DIRECTED 2026-09-03:** *"deal with that right away — I need the wake and wrap tools to be reliable."* **ONE root cause, 4–5 consumer sites:** the transcripts dir is a proxy for *"a session"* and **a Tarbuckle mumble is indistinguishable from a session at the file level.** Sites: `governance-drift-check.py:513` (PENDING-178) · `wake-digest.py:354`→`previous_transcript` (**the false `unattended` alarm of 09-01 — diagnosed, code never changed**) · `wake-digest.py` selftest `_tx[-14:-1]` (**fails every run**) · `tarbuckle-invoke.py:40` (⚠ **SUSPECTED, VERIFY FIRST**). 🔑 **The discriminator already exists and is controlled — `wake-digest.py:932 human_turns()`; this is wiring a tested function into 4 call sites, not building a classifier.** ⚠ **It is `[FIX]`, not `[PROPOSAL]` — my wrap-time classification was wrong**: the control's label already says *"a real session"*, so restoring that population repairs it against its own spec. **Does NOT extend to changing what the `>=84` trigger means** — that stays PENDING-178/REVIEWED-123. **Write the positive control FIRST.** Full census + first steps: ADDENDUM 1 of the session record.
 > 🔑 **THE INDEX HAD BECOME THE RECORD.** `MEMORY.md` breached its load budget and was being **silently truncated at wake** — but the cause was not bulk. Five tracker entries had grown into paragraphs, and for **three the index was the SOLE custodian of live state**: the studium tracker stopped at **2026-08-13** while the index carried engine news to 09-01 · the Fool's only link was a **sealed seed**, with nowhere legitimate to append · L1's replay **mechanism** (`minCursor` is a minimum over 11 modules, two never participate ⇒ pinned at 0 **by construction**) and **completion criterion** (uninterrupted run length, not rate) existed nowhere else. All relocated verbatim; **Tarbuckle got a tracker**. 26,803 → 23,714 (`2171d91`, both remotes verified).
 > ⚠ **PRUNING WOULD HAVE BEEN HARMFUL.** The cut took its rule from the file's own Index discipline — trackers are pointers — and so **left "Rules that fire silently" untouched**: those keep their text inline because they fire when I would not know to look. Cutting the loudest lines would have removed the catches and still left three workstreams undocumented, now deleted rather than truncated.

claude/memory/MEMORY.md

@@ -73,15 +73,15 @@ permalink: claude-memory/memory
 - Chamber-typography — *tracker not yet established*; moves live in per-session memories (2026-05-11 →) + `project-chamber-cruft-restoration.md` + `project-chamber-typography-mining-plan-2026-05-15.md`.
 
 ## Active Session
-> 🔴 **NEXT SESSION — TWO INDEPENDENT ACTS, UNBUNDLED (jurist correction 2026-09-04; the steward's original order was git-init first).** They touch different files and neither depends on the other; **serializing them puts the deadline behind the deliberation.**
+> 🔴 **NEXT SESSION — TWO INDEPENDENT ACTS, UNBUNDLED** (jurist 2026-09-04; steward's original order was git-init first). Different files, no dependency; serializing puts the deadline behind the deliberation.
-> **(A) FIRST — suspend automatic grading at `trigger_fired()`.** This is the act with a **firing distance**: N=65 against 84, **19 away, 13 net in three days**. ⚠ **NOT a repair, NOT a filter, NOT -178 option (b)** — it changes nothing about what the counter counts, so the site-1 exclusion survives intact. ⚠ **IT MUST CARRY A REPLACEMENT BOUND IN THE SAME ACT.** REVIEWED-123 cond. 2 installed *grading at 84* as the freeze's bound; suspending grading **removes exactly that bound** and turns a bounded hold into an open one. Tie the replacement to the joint ruling or to a working session predicate; **the 2026-09-16 report obligation survives either way.** ⚠ Bites **OWED-5**, whose discharge is nowlong-coupled to a ladder-retrieval trial.
+> **(A) FIRST — suspend automatic grading at `trigger_fired()`.** The act with a **firing distance**: N=65/84, **19 away, 13 net in three days**. ⚠ NOT a repair, NOT a filter, NOT -178 option (b) — it changes nothing about what the counter counts, so **the site-1 exclusion survives**. ⚠ **IT MUST CARRY A REPLACEMENT BOUND IN THE SAME ACT:** REVIEWED-123 cond. 2 installed *grading at 84* as the freeze's bound, and suspending grading removes exactly it. The 09-16 report obligation survives either way. Bites **OWED-5**, now long-coupled to a ladder trial.
-> **(B) INDEPENDENTLY — `git init` `~/_Dev/claude-transcript-archive`** (144 MB, no repo, no remote, no second copy; **11 transcripts exist there and nowhere else**). ⚠ **A steward call** — full transcripts are everything ever typed. Until it happens `preserve-transcripts.py:11`'s "git-tracked location" stays false, **which is the correct state for a docstring describing a thing that is not true yet.**
+> **(B) INDEPENDENTLY — `git init` `~/_Dev/claude-transcript-archive`** (144 MB, no repo, no remote; **11 transcripts exist there and nowhere else**). ⚠ **A steward call.** Until then `preserve-transcripts.py:11`'s "git-tracked location" stays false — **the correct state for a docstring describing a thing that is not true yet.**
-> ⚖ **THEN THE JOINT RULING — -178 AND -179 ARE ONE DECIDABLE UNIT.** -179 is -178's evidence and says so **in prose, because the numbering cannot carry it** (PENDING-145). Covers **unit · window · recurrence · predicate · seeding**. ⚠ **Seeding grew a SECOND HALF:** preservation **permanently diverged the two stores** (11 archive-only), so the question is **over which store**, not only what N — **the trigger reads LIVE; honest grading of a post-08-07 population must read PRESERVED.** Steward agrees with **-179 option (c)** and with **not building it now**.
+> ⚖ **THEN THE JOINT RULING — -178 AND -179 ARE ONE DECIDABLE UNIT.** -179 is -178's evidence, in prose, because the numbering cannot carry it (PENDING-145). Covers **unit · window · recurrence · predicate · seeding**. ⚠ **Seeding grew a second half:** preservation **permanently diverged the two stores** (11 archive-only) — the question is **over which store**, and **the trigger reads LIVE while honest grading must read PRESERVED**.
-> 🔑 **THE DISCRIMINATOR WAS A COINCIDENCE — AND THE GATE'S *POSITION* HELD, ITS *CONTENT* DID NOT.** `human_turns()` scores **must-detect 22/24, must-not-flag 35/41**; it skips slash-command markers, and a mumble inherits them **only when the session it quoted had one** — the 2 leaks are exactly the 2 marker-free mumbles. ⚠ **`0` never meant "mumble"; it means "nobody spoke"**, equally true of an unattended session. ⚠ **BUT: gate 2a as SPECIFIED was one arm, one transcript, expected 0 — run as written it GREENS (22/24 return 0).** The finding came from **replacing the specification** with independent whole-population ground truth plus an unrequested second arm. **"Follow the handover" is the wrong lesson; "a gate's existence bought the chance, improving its specification caught it" is the right one.**
+> ⛔ **THE `[FIX]` WARRANT IS VOID AT EVERY SITE — withdrawn 2026-09-04; do not re-derive it.** The predicate is `"wrapped" in _v` and **does not restrict to real sessions at all**, so restoring the population repairs nothing. **The defect was never the sample.** Replacing the selftest is a **rewrite of the predicate against its label**, unavailable under any `[FIX]` reading. ✅ **The selftest date question is RETIRED BY FINDING** — do NOT replay `wrap_events()` git history. ⚠ **OWED-5 catches empty-set vacuity only**; the selftest had 13 in its denominator and still tested nothing about its subject — that is **OWED-1's class, a recurrence not a discovery**.
-> ⚠ **THE FAILING SELFTEST CONTROL DOES NOT TEST ITS OWN CLAIM** (measured live 09-04). Slice = **1 real + 12 mumbles**; verdict `wrapped` = **1 real + 4 MUMBLES**. Predicate `"wrapped" in _v` is **satisfiable by mumbles alone**, so it would pass with zero real sessions. **OWED-1's wrong-subject family, inside the control meant to be evidence about mumbles.** ⚠ **The date of its first failing run is STILL OPEN** — the archive reconstruction is not sound for it (snapshot mtimes; `wrap_events()` not replayed). *"Intermittent" was a framing substituted for the question.*
+> 🔑 **THE LESSON, AND THE COMFORTABLE VERSION IS WRONG.** Gate 2a **as specified** was one arm, one transcript, expected 0 — **run as written it GREENS** (22/24 mumbles return 0). The catch came from **replacing the specification** with whole-population ground truth plus an unrequested second arm. *A gate's existence bought the chance; improving its specification caught it.* ⚠ **Three of -179's four load-bearing claims were corrected within 24 h of filing** — read the rest as provisional.
-> 📌 **STEWARD OWES:** the joint -178/-179 ruling **with a replacement bound** · the archive remote question · `~/.claude/agents` under version control (**before anything else edits it**) · **the moratorium — now 64 open items, and it is shaping filing in BOTH directions (one finding withheld, one filed under protest), the worst state for an undecided rule** · PENDING-171 · -160 · -168 · the §5 regrade (eighth session).
+> 📌 **STEWARD OWES:** the joint -178/-179 ruling **with a replacement bound** · the archive remote question · `~/.claude/agents` under version control (**before anything else edits it**) · **the moratorium — 64 open items, shaping filing in BOTH directions (one withheld, one filed under protest), the worst state for an undecided rule** · PENDING-171 · -160 · -168 · the §5 regrade (eighth session).
 
-- [Session 2026-09-04 — the discriminator was a coincidence](session-2026-09-04-the-discriminator-was-a-coincidence.md) — gate 2a failed and the repairs correctly never happened; PENDING-179 + AMENDMENT 1 (jurist corrections: gate content vs position · 2c's narrowing limit · the selftest's wrong subject · the suspension's missing bound · unbundling). **NEXT: (A) suspend grading with a replacement bound; (B) git init, independently.**
+- [Session 2026-09-04 — the discriminator was a coincidence](session-2026-09-04-the-discriminator-was-a-coincidence.md) — gate 2a failed, repairs correctly never happened; PENDING-179 + AMENDMENTS 1–2 hold the full reasoning (gate content vs position · 2c's narrowing limit · the selftest's wrong subject · the void `[FIX]` warrant · the missing bound · the two vacuity classes · a correlated jurist/executor miss on urgency, for PENDING-89). **NEXT: (A) suspend with a bound; (B) git init, independently.**
 
 ## Historical reference → MEMORY-reference.md
 Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in [MEMORY-reference.md](MEMORY-reference.md) — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent `session-*.md` files (wake §2.b.1).

claude/memory/knowledge-graph.jsonl

@@ -783,3 +783,6 @@
 {"subject": "claude-code", "predicate": "drift-pattern", "object": "A BETTER-FOUNDED FRAMING SUBSTITUTED FOR AN UNANSWERED QUESTION, TWICE. Asked for the DATE of the selftest's first failing run (a start before 2026-08-25 would mean the mumble is not the only cause), the executor returned 'the defect is intermittent, not permanent' — true, better-founded than the prior claim, and not the question. Jurist-caught 2026-09-04. The date remains unestablished; the archive reconstruction is unsound for it (snapshot mtimes, wrap_events not replayed).", "valid_from": "2026-09-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-04-the-discriminator-was-a-coincidence.md", "extracted_at": "2026-09-04"}
 {"subject": "wake-digest.py selftest control 'a real session reads as WRAPPED end-to-end'", "predicate": "does-not-test-its-claim", "object": "WRONG-SUBJECT, measured live 2026-09-04. Slice _tx[-14:-1] holds 1 real session and 12 mumbles; verdict 'wrapped' comes from 1 real session and 4 MUMBLES. The predicate is \"wrapped\" in _v, satisfiable by mumbles alone, so the control would PASS with zero real sessions in the slice. Its label claims a property of real sessions; its test asks whether any transcript whatever drew the verdict. This also supersedes the 2026-09-03 origin claim that all 13 slice members were mumbles and that the cause was mumble-displacement.", "valid_from": "2026-09-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-04-the-discriminator-was-a-coincidence.md", "extracted_at": "2026-09-04"}
 {"subject": "suspending automatic grading at trigger_fired()", "predicate": "removes-the-freeze-bound", "object": "REVIEWED-123 condition 2 installed 'grading at 84' as the bound on the ladder freeze, on the reasoning that a hold with no expiry and no visible distance to expiry becomes permanent. Suspending automatic grading removes exactly that bound and converts a bounded hold into an open one. The suspension ruling must install a replacement bound in the same act — tied to the joint -178/-179 ruling or to a working session predicate — with the 2026-09-16 report obligation surviving either way. Jurist-raised 2026-09-04, self-corrected against their own earlier recommendation.", "valid_from": "2026-09-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-04-the-discriminator-was-a-coincidence.md", "extracted_at": "2026-09-04"}
+{"subject": "the [FIX] reclassification of the wake-digest selftest", "predicate": "void", "object": "WITHDRAWN 2026-09-04. It rested on: the label says 'a real session', the sample has none, so restoring the population repairs it against its own spec. The predicate is `\"wrapped\" in _v` and does not restrict to real sessions at all -- restoring the population repairs nothing, and the test would pass on a correctly-populated slice where every real session failed. The defect was never the sample; label and test disagree about SUBJECT. Sites 2 and 4 never had a quoted specification; site 3's is contradicted by its own implementation. Nothing in the four-site census is [FIX]-warranted, and replacing the selftest is a rewrite of the predicate against its label.", "valid_from": "2026-09-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-04-the-discriminator-was-a-coincidence.md", "extracted_at": "2026-09-04"}
+{"subject": "two vacuity classes in controls", "predicate": "distinction", "object": "EMPTY-SET VACUITY (no cases at all) is what OWED-5's denominator rule catches. WRONG-SUBJECT VACUITY (full denominator, predicate does not implement the subject named in the label) is OWED-1's family and is INVISIBLE to OWED-5. The wake-digest selftest is the demonstrated instance: 13 files in its denominator, passes the denominator rule, tests nothing about its subject. A fleet denominator sweep therefore establishes nothing about whether controls test what they claim. Recorded so OWED-5 is not over-trusted for having been earned the same week.", "valid_from": "2026-09-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-04-the-discriminator-was-a-coincidence.md", "extracted_at": "2026-09-04"}
+{"subject": "claude-code and claude-app (jurist)", "predicate": "correlated-miss", "object": "BOTH READ THE ABSENCE OF A STATED RATE AS THE ABSENCE OF URGENCY, and neither flagged the ladder trigger's firing distance until a measured N of 65 arrived. PENDING-178 and -147 correctly withheld a rate; both parties treated that withholding as slack. The jurist named it as a CLASS error in its own disposition and declined credit for self-correcting, on the ground that correction arrived only with new data. What one missed, the other missed too, same direction, same reason. Logged per Constitutional Constraint 6, which requires evidence against the differently-biased-checkers doctrine to be recorded when observed rather than only when sought. Belongs to PENDING-89's docket.", "valid_from": "2026-09-04", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-04-the-discriminator-was-a-coincidence.md", "extracted_at": "2026-09-04"}

claude/memory/session-2026-09-03-the-index-had-become-the-record.md

@@ -245,3 +245,28 @@ stays the steward's, because REVIEWED-123's freeze is measuring against that cou
 4. **Do not let the count of sites become the measure of done.** The question the steward asked is
    whether the tools are reliable, and a fourth site found later is a better outcome than four sites
    fixed and the class declared closed.
+
+
+---
+
+## ⛔ SUPERSEDED — ADDENDUM 1's `[FIX]` reclassification is void (added 2026-09-04)
+
+ADDENDUM 1 above argued: *"The control's own label states its predicate: 'a real session reads as
+WRAPPED end-to-end.' Its sample contains no real sessions, so the code does not do what it already
+says it does. Restoring the population the label names is repairing an instrument against its
+existing specification — `[FIX]`."*
+
+**That argument is void.** Read at source, the predicate is `"wrapped" in _v` — it does not restrict
+to real sessions anywhere. Restoring the population therefore 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.**
+
+Also superseded here: **"all 13 are Tarbuckle mumbles"** — measured live 2026-09-04, the slice holds
+**1 real session and 12 mumbles**, and **4 of the mumbles read as `wrapped`**.
+
+⚠ **Nothing in the four-site census is `[FIX]`-warranted.** Sites 2 and 4 never had a quoted
+specification; site 3's is contradicted by its own implementation. Whatever replaces the selftest is
+a **rewrite of the predicate against its label** — a larger act than the one reclassified.
+
+Full reasoning: `PENDING-179 AMENDMENT 2`, and
+[[session-2026-09-04-the-discriminator-was-a-coincidence]].

claude/memory/session-2026-09-04-the-discriminator-was-a-coincidence.md

@@ -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.