[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/knowledge-graph.jsonl

@@ -779,3 +779,7 @@
 {"subject": "the rule 'a null search is evidence about the QUERY'", "predicate": "prevention", "object": "STOPPED A VACUOUS PASS FROM CERTIFYING A BROKEN DISCRIMINATOR, 2026-09-03. The rule was banked 2026-08-31 after four name-search errors in two sessions -- a different failure class entirely (reporting 'you don't have X' from a filename search). Here it fired on a control's empty denominator and prevented a broken predicate being wired into three further consumer sites. A lesson banked from one class stopping another is the transfer signature.", "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": "~/_Dev/claude-transcript-archive", "predicate": "is-not-version-controlled", "object": "NO .git, no parent repo, 144 MB, single copy on one disk -- while preserve-transcripts.py:11 states it copies transcripts 'to a git-tracked location so the population stops shrinking'. 11 transcripts have been pruned at source and exist ONLY here. PENDING-144's class (substrate claims inside governance scripts checked by nothing) at the site where it costs most, because the docstring is what a reader consults to decide whether the evidence is safe. Steward directed a git init as the next session's first act.", "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 ladder trial counter", "predicate": "composition", "object": "N-now 65 of 84 measured 2026-09-03 = 41 real sessions + 24 Tarbuckle mumbles (36.9% machine chatter). Rising fast. The prior record in MEMORY.md said 44 and falling ('shedding faster than it gains') -- wrong in the number and backwards in the direction; corrected record-only. Also: preservation has permanently diverged the two stores (11 archive-only files), so grading must now specify WHICH STORE, not only what N -- the trigger reads live, honest grading of a post-08-07 population must read preserved.", "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", "predicate": "drift-pattern", "object": "CREDITED THE GATE'S CONTENT WHEN ONLY ITS POSITION HELD. The wrap recorded 'the handover's ordering, at every point it was load-bearing.' 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 existed only because the executor replaced the specification with independent whole-population ground truth and added an unrequested must-not-flag arm. Jurist-caught 2026-09-04. The comfortable lesson ('follow handovers') would have had the next session run the next gate as written.", "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", "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"}