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
This commit is contained in:
David F Glidden
2026-08-25 19:42:14 +02:00
co-authored by Claude Opus 5
parent e19b4cc303
commit 938c05c71e
2 changed files with 93 additions and 0 deletions
+19
View File
@@ -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.