From b97e77aebe4b8ed51fb8d57976c9ebc9eb76699b Mon Sep 17 00:00:00 2001 From: David F Glidden Date: Wed, 5 Aug 2026 21:18:08 +0200 Subject: [PATCH] docs(governance): PENDING-86 (a) authorized and landed; (d) still open MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Records the steward authorization, what shipped, the superseded-header trap the change had to disclose, and the restart requirement. (d) — keyword search — is explicitly NOT folded in: the jurist asked for (a)+(d) together and (d) is a new tool surface, not two enum entries. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01AB3Kryoy6b1pm2Nz1DYdLh --- PENDING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/PENDING.md b/PENDING.md index 92aea16..8174385 100644 --- a/PENDING.md +++ b/PENDING.md @@ -676,6 +676,11 @@ Executed as §VII eyeball-after-gate: pages rendered with `pdftoppm` and read, n **Awaiting:** Steward authorization — it widens what the jurist can read, which is the steward's call, not the executor's. **Amendment 2026-07-29 (PENDING-87 / REVIEWED-84 process note, jurist-raised, not ruled):** a **second, independent** instance of this item's failure, and it sharpens the diagnosis. The jurist's REVIEWED-83 Q3 demanded an outcome REVIEWED-74 had already established was impossible — a ruling **four days older**, in a file the jurist *could* read, but had no reason to open, *"since nothing in the package I ruled on mentioned order or Eichmann at all."* So the gap is not only **"the jurist cannot read the constitution it design-gates"** but **"the jurist cannot discover a relevant prior ruling whose ID it does not already know."** Keyed retrieval cannot fix that; only search can — hence option (d). The jurist directed this be folded here rather than opened as a new item. +**AUTHORIZED + LANDED 2026-08-05 — option (a) only.** Steward-authorized on the jurist's own request while it was unable to close PENDING-99's Q2 (a question turning on §II.3's *"inline anchor marker"* and §V's marker exclusion). `governance-mcp.py` gains two enum keys — `chamber-spec`, `graduation-spec` (`5cd5faf`). No new tool, no path argument, no traversal surface; every existing refusal control still passes. Selftest **29 → 35 controls, 0 fail**; live stdio round-trip confirms the §V clause arrives verbatim. +⚠ **Reachability of the key is not reachability of the clause**, and this nearly went wrong: the constitution's operative sections start near line 354, above which sit ~330 lines of **superseded** version headers. A jurist reading at the default `limit=400` lands in obsoleted text — the new access *causing* the misruling it exists to prevent. The trap is now disclosed on the key's own description, with two controls pinning it: the §II.3 and §V clauses are both reachable in one paged call (`offset=350, limit=2000`), and a **negative control** confirms a first-page read does land in the `(obsoleted)` region. +⚠ **Requires a Claude.app restart** — the running server carries the old code until respawned. +**Still open on this item:** **(d)**, keyword search across `PENDING.md`/`PENDING-archive.md`/`REVIEWED.md`. The jurist asked for (a)+(d) together; (d) is a new tool surface rather than two enum entries, so it was not folded in silently. **(b)** stands built and in use (`check_containment.py`, applied to the PENDING-99 package: 16/16 contained, 9/9 controls absent). + **Amendment 2026-08-02 (third instance, jurist-raised in REVIEWED-86):** the jurist could not reach `contamination-problem.md` — *"same gap as the skill files last time, now touching the part of the argument that establishes the doctrine actually has a gap to fill"* — and called this *"a second, independent argument for it"*. So the tally is now three distinct documents the jurist has been unable to read while design-gating work that turns on them: the chamber constitution, the skill files, and now a CapableMind methodology doc. **The workaround was built rather than proposed this time:** `dotfiles/claude/governance/check_containment.py`, positive controls mandatory, which discharged REVIEWED-85's stated precondition (7/7 contained, 5/5 controls absent) and caught a fabricated terminal period in the executor's own package. That is evidence option (b) is *workable*, not merely proposable — and it bears on the (a)/(b)/(c)/(d) choice, which remains the steward's. ## PENDING-87 — Order attestation: the REVIEWED-83 Q3 precondition is unsatisfiable as written