session 2026-07-27 evening: PENDING-76/77/78 placed; governance drift-check built + wired into /wake-up

PENDING-76 remanded by jurist — required count returned 0 of 11 (the package's own
IV.2 refinement proved its target category empty); executor recommends withdrawal.
PENDING-77 (5 structural defects) and PENDING-78 (.app preferences) released by the
ruling from needing it. Drift check reports contradicted state claims at every wake
and corrects nothing — detection needs no authorization, correction does.

MEMORY.md compacted 20.5KB -> 17.1KB (budget hook); prior Active Session demoted to
MEMORY-reference.md. CLAUDE.md and REVIEWED.md untouched.

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

PENDING.md

@@ -1726,3 +1726,45 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
 **RULED 2026-07-25 — design-gate PASSED, with one REQUIRED correction** (`docs/kind-scoping-verification-JURIST-RULING-2026-07-25.md`). The jurist **adopted the package's Part-4 argument over his own framing**: the foreclosure is not that a non-text work *fails* the criterion but that the criterion is **VACUOUS** on it (empty re-extraction is trivially prose-word-identical to itself) — the false-positive shape, caught prospectively for the first time rather than after a finding. **Required correction:** Edit 1's *"that method is prose-word identity … (V-DSL · V-TEXT · V-SCAN)"* **overstates against V-SCAN**, whose ratified row says *no ground-truth text* and whose bar is *"a distinct, named, more-expensive criterion — not the deterministic bar relaxed"* — the scoping sentence must not flatten a distinction the table already draws. **Q1** placement at the evidence-tiers preamble CONFIRMED (that is where method is *defined*; tier-1 would scope the bar and leave the definition unscoped). **Q2** guard kept and **rebound to the property, not enrollment** (*"a text-bearing work … no work may weaken its applicable method"*) — as drafted it reached only existing kinds and would open the moment the door is first used. **Q3** Edit 3's correction ACCEPTED, the jurist's `line_frame` shape WITHDRAWN (3rd substrate-refutes-composed-shape this session); the heavier rename correctly declined. **Q4** PROPOSAL/MINOR confirmed, the FIX reading **declined on the vacuity argument**. **Q5** Edit 2 kept (§V reads as a prose-framed universal alone; cross-section inference is what a successor cannot be assumed to perform). **Carry-forward for the REVIEWED entry, NOT spec text:** the primitives that would serve a future non-text kind already exist ratified (character-bearing image = content, hash-fixed, catalogued normalization, never silently dropped — REVIEWED-70 Q3; the Loeb sidecar's typed `{kind:'glyph', file:…}`) — nothing reserved, nothing promised, but a successor should find in the record that the architecture already pointed that way.
 **BUILT + LANDED 2026-07-25 (steward-authorized verbally; REVIEWED-75 placement 2026-07-27):** spec **v2.7.0** (v2.6.0 frozen `-v2.6.0.md`; **bounded-diff proven** — 1 deletion [the title line, reappearing as `(obsoleted)`] + 3 hunks [header stack · §V +6 · evidence-tiers +16], every other line v2.6.0 byte-preserved), both corrections applied verbatim to the ruling, + the sidecar-schema **generality note** (FIX) with its amendment-log row. Fleet 248/248 (doc-only change, baseline unmoved). CLAUDE.md brought current.
 **CLOSED 2026-07-27 — REVIEWED-75 PLACED** (`REVIEWED.md:710`). Landed as spec v2.7.0 (`e3b6aef`) + the sidecar-schema generality note; both required corrections applied against the live wording as the ruling directed. Nothing outstanding on this item. Related: REVIEWED-64 (`line_frame`/the declaration principle), REVIEWED-70 (§V character-as-image), REVIEWED-56 (sidecar additive-only lock discipline).
+
+## PENDING-76 — Authorization class follows claim class (REMANDED; executor recommends withdrawal)
+**Date:** 2026-07-27
+**Tag:** [ESCALATE]
+**Summary:** Proposed amending Constitutional Constraint #1 so a state claim verifiable by command becomes `[FIX]` while doctrine stays `[ESCALATE]`. **Jurist remanded; the required count returns 0; executor recommends withdrawal rather than re-posing.**
+**Rationale:** `~/CLAUDE.md` carried 11 substrate-contradicted state claims for up to 4 months because detection and correction were priced identically — L113 requires drift to be *flagged*, L103/L253 make correcting it cost what amending doctrine costs. Package: `~/_Dev/CapableMind-AI/docs/thinking/David/governance-currency-JURIST-PACKAGE-2026-07-27.md`.
+**RULED 2026-07-27 — NOT GRANTED AS DRAFTED, remanded with one required number.** The jurist ran the package's own Part IV.2 refinement (*the verifying command's output must be the evidence*) back across its Part II census — which the executor had not done — and found the evidence and the remedy do not meet. Required back: the count of currently-false lines cleanly `[FIX]`-eligible under IV.2. **Q2 RATIFIED and severed as a standing epistemic standard, effective immediately**, with one addition: *a negative command result requires a positive control* — an absence proves nothing until the instrument is shown capable of detecting presence. **Q3** answered *no* (8 mixed lines against 32 non-doctrine = 25% ambiguity at the margin; single-party classification unsafe at that rate). **Q4** wrong mechanism — prefer sunset to revocation, since revocation-on-misuse requires the misusing party to detect it. **Q5** the eval cannot bear a constitutional edit: 3 tasks contain no tail, so guardrail redundancy was never measurable; the 3× cost gap is robust, the redundancy finding is not.
+**COUNT RETURNED 2026-07-27 — 0 of 11.** Per-line working in `claude-md-gate-return-2026-07-27.md`. Every false state claim is either steward-held (the 2 expired horizons) or welded to a directive (the 9 MemPalace claims, L148) — and *"where a line is both, it is doctrine"*, the package's own tiebreaker, escalates all of them. What remains `[FIX]`-eligible is 5 defects, **entirely structural, zero state**. The amendment is titled and argued around a category it would not free a single member of.
+**Recommendation: WITHDRAW.** Do not re-pose. Two live successors, neither urgent: (a) the jurist's framing challenge — the MemPalace section and Active Projects horizons are *operational configuration filed in a constitutional instrument*, so the disease is a category error and the remedy is extraction, not amendment; (b) if freeing structural repair is wanted on its own, a clause a tenth this size (*repair that changes no semantic content is `[FIX]`*) achieves it with no burden inversion.
+**Mitigation landed without authorization (detection ≠ correction):** `~/dotfiles/scripts/governance-drift-check.py`, wired into `/wake-up` §2.c. Reports the contradicted claims at every wake; corrects nothing. Staleness is now visible rather than misleading — Constitutional Constraint #4 applied to the governance document itself.
+**Files affected:** none. Nothing modified.
+**Awaiting:** Steward — withdraw, or re-pose against the extraction framing.
+
+## PENDING-77 — CLAUDE.md structural repair (5 defects, no semantic change)
+**Date:** 2026-07-27
+**Tag:** [ESCALATE]
+**Summary:** Five mechanical defects in `~/CLAUDE.md`, none altering meaning. Released by the jurist from the PENDING-76 remand — *"they do not need this ruling."*
+**Rationale:** §Active Projects does not render as a table, and §Constitutional Constraints — the section governing what the executor may not do — is left nested beneath an unrelated empty stub.
+**The five, in required order** (drift-check verified, `governance-drift-check.py`):
+1. **EOF** — no terminal newline; `wc -l` reports 257 for a 258-line file. **Apply first** or every line reference below shifts by one.
+2. **L241, L242** — stray leading whitespace on table rows.
+3. **L243** — two rows fused on one line (`|| **Compass** |`); the Compass row does not render.
+4. **L242–243** — mid-cell hard line break inside the L2 row.
+5. **L248** — empty `### L1 Active Workstream (2026-04-19)` stub (with trailing whitespace) running directly into `## Constitutional Constraints`.
+**Exact old/new text with line numbers:** `claude-md-proposals-2026-07-27.md` §PENDING-C through §PENDING-F.
+**Scope boundary:** structural only. The expired horizons on L241–242 and the "Stewart" typo are **excluded** — the first is steward-held state, the second requires knowing an intended spelling that no command establishes.
+**Verification:** re-run `governance-drift-check.py`; the five findings should disappear and the count drop from 9 to 4.
+**Files affected:** `~/dotfiles/CLAUDE.md`.
+**Awaiting:** Steward authorization.
+
+## PENDING-78 — Claude.app personal preferences: three verified-false claims
+**Date:** 2026-07-27
+**Tag:** [ESCALATE] — steward-held document; the executor verifies, the steward edits.
+**Summary:** The `.app` preferences carry the same drift class as `~/CLAUDE.md`, including one identical stale pointer. **Jurist: outside the amendment's reach entirely** — not `~/CLAUDE.md`, not governed by L253, so no outcome on PENDING-76 touches this.
+**Verified false 2026-07-27:**
+1. *"branch: `fix/replay-durability-contracts`"* — merged as `c9746ae`; `HEAD` is `main`. The identical stale pointer also heads this file (`PENDING.md` L3).
+2. *"`COWORK.md`"* named as a governance document — no such file exists anywhere under `~`; the only `cowork*` hits are Claude Desktop application internals.
+3. *"L2 constitutional governance is blocked pending L1 stability"* — L1 has 0 commits in 14 days. Blocked pending something dormant is not a governance state.
+**Also observed, not proposed:** ARC described as *"near-operational"* (Stage G sealed; 152 commits/60d, understated); chamber-library and studium-engine absent (183 and 41 commits/60d).
+**⚑ For the steward and jurist, not the executor:** The Chamber is named in the `.app` preferences and **absent from `~/CLAUDE.md`**. The jurist ruled this *"the most consequential single finding in the package"* and noted the executor had filed it as a footnote: *"The jurist knowing about work the executor is blind to is not a documentation defect. It is a governance model with two parties holding different maps."*
+**Files affected:** Claude.app personal preferences (steward-held). Executor modifies nothing.
+**Awaiting:** Steward edit; jurist review of the asymmetry.