[HARDENING] PENDING-179 AMENDMENT 1: jurist corrections, and the selftest control does not test its own claim

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

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

@@ -220,3 +220,78 @@ computable without changing any of them. ⚠ If the answer is zero, OWED-5 is a
 accident and should be labelled that way rather than carried as a general finding. If it is more than
 zero, then some number of currently-green controls have never tested anything — and nobody knows
 which, because a vacuous pass and a real pass print the same word.
+
+---
+
+## ADDENDUM 1 — after the wrap: the jurist corrects the record, and one claim in it was wrong
+
+⚠ **Appended 2026-09-04 after the session record was written, committed and pushed.** The jurist read
+the wrap and returned five corrections, two operational. Filed into `PENDING-179 AMENDMENT 1`; the
+substance is repeated here because this file is what the next wake reads.
+
+### The correction that matters most — I gave credit to the wrong thing
+
+The wrap said *"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** — 22 of 24 mumbles return 0, so a single sampled mumble passes with ~92%
+probability and the repair proceeds. The finding exists because I **replaced the specification**:
+ground truth taken independently of the function under test, across the whole population, plus a
+`must-not-flag` arm nobody asked for.
+
+⚠ **"Handovers are load-bearing, follow them" is the wrong lesson and the more comfortable one.**
+*A gate's existence bought the chance to catch this; improving on the gate's specification is what
+caught it.* A session inheriting the comfortable version runs the next gate as written.
+
+### A NEW measurement that supersedes this session's own origin claim
+
+The 2026-09-03 record said the failing selftest sampled 13 transcripts and *"all thirteen are
+Tarbuckle mumbles"*, with mumble-displacement as the cause. **Measured live on the actual slice:**
+
+- **1 real session, 12 mumbles** — not 13 mumbles.
+- **verdict `wrapped`: 1 from the real session, 4 FROM MUMBLES.**
+- the predicate is `"wrapped" in _v` — **satisfiable by mumbles alone.** It would pass with **zero**
+  real sessions in the slice.
+
+⚠ **Its label claims "a real session reads as WRAPPED end-to-end"; its test asks whether any
+transcript whatever drew that verdict.** That is **OWED-1's wrong-subject family, inside the control
+that was supposed to be evidence about mumbles.**
+
+### And the question I still have not answered
+
+The jurist asked for **the date of the control's first failing run**, because a start predating
+2026-08-25 would mean the mumble is not its only cause. A reconstruction over the preserved archive
+found no date from 08-20 to 09-04 on which the slice held zero real sessions — **but that
+reconstruction is not sound for the purpose**: manifest `source_mtime` is snapshot-time rather than
+current, and the verdict also depends on `wrap_events()` git history that was not replayed.
+⚠ **OPEN, not answered.** The wrap's *"intermittent"* was a better-founded description **substituted
+for the question** — the same move twice, and naming it is the correction.
+
+### Two operational changes for the next session
+
+1. **UNBUNDLE the two acts, suspension first.** The wrap's own *decisions deferred* records the
+   `git init` as a **steward call**, so it may wait days — while the suspension is the act with a
+   **firing distance** (N=65/84, 19 away, 13 net in three days). Different files, no dependency;
+   serializing puts the deadline behind the deliberation.
+2. **THE SUSPENSION MUST CARRY A REPLACEMENT BOUND IN THE SAME ACT.** REVIEWED-123 cond. 2 installed
+   *grading at 84* as the freeze's bound — *"a hold with no expiry and no visible distance to expiry
+   is how a temporary freeze becomes a permanent one."* Suspending grading **removes exactly that
+   bound.** Tie the replacement to the joint ruling or to a working session predicate; the 09-16
+   report obligation survives either way. ⚠ Bites **OWED-5**, now long-coupled to a ladder trial.
+
+### Also carried, and also mine to have missed
+
+**Gate 2c's census limitation is in the wrap but was not in PENDING-179** — which is what gets ruled
+on. It was narrowed three times, and repeated narrowing can terminate by confirming the sites the
+predicate was built around. Now in AMENDMENT 1; **read 2c's "no additional consumers" as the weakest
+of the three findings.**
+
+**The moratorium is still undecided at 64 open items**, and it is shaping filing in **both**
+directions — one finding withheld on 09-03, one filed under protest on 09-03. That is the worst
+state for an undecided rule to sit in.
+
+### What the jurist credited, recorded because credits are evidence too
+
+The vacuous `0/0` was caught by a **standing rule** (*a null search is evidence about the query*),
+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.