[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/MEMORY.md

@@ -73,14 +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, FIRST WORK — STEWARD-DIRECTED 2026-09-04, in this order:** **(1) `git init` the transcript archive** (`~/_Dev/claude-transcript-archive`, 144 MB, currently **no repo, no remote, no second copy** — and `preserve-transcripts.py:11` already *claims* it is git-tracked; **11 transcripts exist there and nowhere else**, so the init is what makes an existing false docstring true rather than requiring it be edited into honesty). **(2) Suspend the automatic grading at `trigger_fired()`.** ⚠ **The steward's precision here is the point: 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 prevents a grade firing on a population whose contamination is measured and rising.
-> ⚖ **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). The ruling covers **unit · window · recurrence · predicate · seeding**. ⚠ **Seeding has grown a SECOND HALF, new on 09-04:** preservation has **permanently diverged the two stores** — 11 files exist only in the archive — so the question is no longer only *what N* but **over which store**, and **the trigger reads LIVE while any honest grading of a post-08-07 population must read PRESERVED.** Steward's recorded positions: **agrees with -179's option (c)** (a mumble that declares itself cannot be misread by a marker coincidence) **and with its refusal to build it now**.
-> 🔑 **THE DISCRIMINATOR WAS A COINCIDENCE, AND THE GATE IS WHAT CAUGHT IT.** The whole repair plan rested on *"human_turns() already exists and is controlled — this is wiring, not classifier-building."* **False.** Against ground truth from the fool's own prompt text: **must-detect 22/24, must-not-flag 35/41.** It skips slash-command markers, and a mumble inherits those markers **only when the session it quoted happened to contain one** — **the 2 leaks are exactly the 2 marker-free mumbles.** ⚠ **`0` never meant "mumble"; it means "nobody spoke", which is equally true of an unattended real session** (`b7e7eb39`, PENDING-172). **No repair made, no replacement built** — three controls passed and a fourth broke, so the finding is **the control set**: all three tested the question the function was *for*, none the question it was *reused* for. **That lesson generalizes past this function** (steward, 09-04).
-> ⚠ **THE HANDOVER DID NOT IMPROVE THE FIX; IT PREVENTED IT.** Preservation first (it expires), site-1 excluded on receipt, repair gated behind three read-only checks. Left to my own plan I would have written a positive control for a *fixture* and wired a broken predicate into three more sites, all of it green.
-> 📌 **MEASURED, AND THE DIRECTION HAD BEEN RECORDED BACKWARDS:** N-now **65/84** — **41 real + 24 mumble (36.9%)**. The index had carried *"44, DOWN 7, shedding faster than it gains"*; it is **rising fast and for the wrong reason**. Corrected record-only (`c150bdf`, both remotes verified).
-> 📌 **STEWARD OWES:** the joint -178/-179 ruling · the **archive remote question** (144 MB; full transcripts = everything ever typed) · `~/.claude/agents` under version control (**before anything else edits it**) · the **moratorium decision** · PENDING-171 · -160 · -168 · the §5 regrade (eighth 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.**
+> **(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.
+> **(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.**
+> ⚖ **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**.
+> 🔑 **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 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.*
+> 📌 **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).
 
-- [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 filed as an item (not a -178 addendum, per -145's suppression mechanism); OWED-5 queued; the transcript archive found unbacked-up while its own script claims otherwise. **NEXT: the two steward-set acts, then the joint ruling.**
+- [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.**
 
 ## 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).