Commit Graph
2 Commits
Author SHA1 Message Date
David F GliddenandClaude Opus 5 9fba331e3e [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
2026-09-04 10:53:40 +02:00
David F GliddenandClaude Opus 5 c150bdff17 [HARDENING] The mumble discriminator fails its own must-detect gate; repairs stopped at the gate (PENDING-179)
The 2026-09-03 repair plan rested on one claim: that human_turns() is an
existing, controlled discriminator, and wiring it into four transcript
consumer sites was plumbing rather than classifier-building.

Tested against ground truth taken from the fool's own prompt text — not from
the function under test — the claim is false. 24 known mumbles, 41 known
non-mumbles, out of 65 transcripts:

  must-detect    22/24  two mumbles read as human-attended
  must-not-flag  35/41  and one "failure" is correct — b7e7eb39 is the
                        unattended session of 2026-08-31, which genuinely
                        has no human turn

human_turns() == 0 never meant "mumble". It means "nobody spoke", which is
equally true of an unattended real session. A mumble embeds the previous
session's text and so inherits its slash-command markers; it is excluded
only when the session it quoted happened to contain one. The two leaks are
exactly the two marker-free mumbles. Coincidence, not design.

No repair was made at any site, and no replacement discriminator was built.
Three controls passed and a fourth broke: all three test the question the
function was built for, none could see the question it was being reused for.
A successor written now inherits whatever made the first set look sufficient.

Also here, per the 2026-09-03 handover:
  - step 0 preservation ran: 76 transcripts, read-back PASS, 11 of them
    already pruned at source and surviving only in the archive
  - gate 2b: the composition claim in PENDING-178 stands (11 mumbles,
    ~a fifth, on 08-31). Two terms do not close and are reported as an open
    disagreement, not a correction — the reconstruction is a demonstrated
    lower bound and -178 enumerated live
  - gate 2c: five sites in four files; -178's [HARDENING] scope holds
  - MEMORY.md record-only arithmetic correction: N-now 44 -> 65 measured,
    composition 41 real + 24 mumble added, direction reversed (it is rising,
    not shedding), stale :331 pointer corrected to :513

Filed as an item rather than a PENDING-178 addendum on PENDING-145's
mechanism: a ruling claims a number, so an addendum would be suppressed the
moment -178 is ruled. The undecided filing moratorium is disclosed inside
the item.

governance-drift-check.py:513 excluded on receipt and not examined.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
2026-09-04 10:22:23 +02:00