REVIEWED-129 AMENDMENT 1 drafted: the premise was false in TWO places

Drafting the correction found a second falsehood in the same sentence. 'PENDING-82, still
open' — its own Awaiting line reads INSTALLED AND IN USE. CLOSED 2026-08-08. Seventeen days.

How it got in is a finding about an instrument, not an excuse: PENDING-82 sits in the wake
digest's OPEN AUTHORIZATION ITEMS list, which is where I read it. Census afterwards: 1 item
of 105 declares itself closed in its own Awaiting line while the open list still carries
it. Four others are partially discharged and genuinely ambiguous — PENDING-146's subject,
not this defect. One confirmed instance, and the item says so at that strength, because 'the
open list is unreliable' from n=1 would be this item repeating its own error in the other
direction.

The draft AMENDS AND JOINS rather than replaces, and says so at the top: register integrity
treats an amendment overwriting its own record as a defect, earned when REVIEWED-87 was
replaced by its own amendment and nothing detected it.

The decision is untouched. Option 1 stands, PENDING-159 stays closed, option 3 stays closed
on the jurist's better ground. What changes is that the ruling now says something true
about why.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf

PENDING.md

@@ -5721,5 +5721,24 @@ A control asserts *this function, given this input, returns this output.* The fa
 - **The correct phrasing:** *the jurist has bounded, read-only, enumerated access to governance files, and no access to any surface through which the fool speaks.* Narrower, true, and it supports the same conclusion.
 - ⚠ **PENDING-82** ("Read-only MCP server: giving the jurist eyes on the substrate") should be checked against this: it is listed OPEN, and something answering its description is running. Whether 14 enumerated files discharge it or merely part of it is not the executor's call.
 
+#### ⚠ A SECOND false claim in the same sentence, found while drafting the correction
+
+*"that is **PENDING-82, still open**"* — **PENDING-82's own `Awaiting` line reads "INSTALLED
+AND IN USE. CLOSED 2026-08-08."** Closed for seventeen days.
+
+**How it got in, and it is a finding about an instrument:** PENDING-82 appears in the wake
+digest's **OPEN AUTHORIZATION ITEMS** list, which is where the executor read it. A census
+afterwards: **1 item of 105 declares itself closed in its own `Awaiting` line while the
+open list still carries it** — that one. Four others are *partially* discharged and
+genuinely ambiguous, which is **PENDING-146's subject**, not this defect. ⚠ **One confirmed
+instance. Stated at that strength deliberately** — a "the open list is unreliable" claim is
+not supported by n=1 and would be this item repeating its own error in the other direction.
+
+**Consequential:** PENDING-82 to `PENDING-archive.md`, or the parser taught to read closure
+lines. Not the executor's call which.
+
+**Draft correction:** `claude/governance/REVIEWED-129-AMENDMENT-1-draft-for-placement.md`
+— written to **JOIN** REVIEWED-129, never to replace it.
+
 **Files affected:** none by the executor. `~/REVIEWED.md` correction is the steward's.
 **Awaiting:** steward.

claude/governance/REVIEWED-129-AMENDMENT-1-draft-for-placement.md

@@ -0,0 +1,74 @@
+# Draft for steward placement — REVIEWED-129 AMENDMENT 1
+
+⚠ **This AMENDS and must JOIN the existing REVIEWED-129, not replace it.** Register
+integrity treats an amendment that overwrites the record it amends as a defect — earned
+2026-08-07 when REVIEWED-87's original was replaced by its own amendment and nothing
+detected it. **Append this block directly after REVIEWED-129; change nothing above it.**
+
+Copy the fenced block into `~/dotfiles/REVIEWED.md`.
+
+---
+
+```markdown
+## REVIEWED-129 — AMENDMENT 1 (2026-08-25): the premise was false in two places; the ruling stands
+**Date:** 2026-08-25
+**Decision:** The decision is UNCHANGED — option 1, REJECTED, PENDING-159 closed. This
+amends the REASONING only, and joins the record above rather than replacing it.
+**Raised by:** the executor, against its own text, within hours of it being placed.
+Filed as PENDING-161 `[ESCALATE]`.
+
+**The sentence at fault, in the ruling and in PENDING-159 (a):**
+
+> *"The jurist is Claude.app and **has no substrate access**; that is **PENDING-82, still
+> open**."*
+
+**Both halves are false.**
+
+**(1) The jurist has substrate access.** `scripts/governance-mcp.py` is registered in
+`~/Library/Application Support/Claude/claude_desktop_config.json` and exposes
+`governance_state`, `governance_item`, `governance_read`, `governance_search`,
+`governance_drift`, `governance_repo`. `governance_read` serves **14 enumerated files** —
+`pending`, `reviewed`, `claude-md`, `memory-index`, the chamber and harness specs, the
+mauss fixtures — *"no path argument by design."* **REVIEWED-126 records the jurist
+"reading the item verbatim via `governance-mcp.py`"** — in this same register, one day
+earlier.
+
+**(2) PENDING-82 is not open.** Its own `Awaiting` line reads **"INSTALLED AND IN USE.
+CLOSED 2026-08-08."** It has been closed for seventeen days.
+
+**The correct phrasing, which supports the same conclusion:** *the jurist has bounded,
+read-only, enumerated access to governance documents, and no access to any surface
+through which the fool speaks.*
+
+**⚠ WHY THE RULING SURVIVES INTACT.** A read surface for enumerated governance FILES
+delivers no status line, no hook `systemMessage`, and no CLI the jurist could run.
+Tarbuckle still cannot speak in a jurist conversation; §9's *"or jurist yields the floor"*
+is still unreachable; option 3 is still closed — **and on the jurist's own and better
+ground, that reading his output would be adjudication and would collapse the position into
+a fourth checker.** Nothing decided here is disturbed. What changes is that the ruling now
+says something true about why.
+
+**⚠ THIS IS THE THIRD INSTANCE OF ONE PATTERN IN ONE DAY, AND THE ONLY ONE THAT REACHED A
+PLACED RULING.** The record's own words for it: *a conclusion that retains its old
+reasoning after that reasoning is falsified is how a false premise survives its own
+refutation.* The other two were caught inside PENDING items (PENDING-152's tick mechanism;
+PENDING-151's "55 files"). **This one was placed, and it was written by the party that
+spent that same day building a mechanism against unverified negative state-claims — hours
+after building it, carrying no `STATE-CLAIM` marker.**
+
+**⚠ HOW THE SECOND ERROR GOT IN, which is a finding about an instrument rather than an
+excuse.** PENDING-82 appears in the wake digest's **"OPEN AUTHORIZATION ITEMS"** list,
+where the executor read it. A census run afterwards found **1 item of 105 whose own
+`Awaiting` line declares it closed while the open list still carries it** — PENDING-82,
+the one relied upon. Four further items are *partially* discharged and are genuinely
+ambiguous, which is **PENDING-146's subject** (*"the open list's unit is the ID; the
+decidable unit is the clause"*) and is not a defect of the same kind. **One confirmed
+instance, not a systemic failure — stated at that strength deliberately.**
+
+**Consequential:** PENDING-82 should be moved to `PENDING-archive.md`, or the open-list
+parser taught to read its own closure line. **Not the executor's call which**, and filed
+rather than done.
+
+**If AUTHORIZED:** Place this block after REVIEWED-129, leaving that entry unchanged. The
+decision needs no re-ruling. PENDING-161 closes with it.
+```