dotfiles/PENDING.md

PENDING.md — Authorization Boundary Log

Protocol: Claude Code appends here at every authorization boundary. David and Claude.app review; decisions are recorded in REVIEWED.md. An item is closed when a matching REVIEWED-N exists there, or when its own header says so. Scope: all workstreams — L1/BMF, chamber-library, studium-engine, ARC, Be, governance. Item families: PENDING-<n> (numeric, the main series) · PENDING-S<n> (skill/protocol series) · PENDING — <name> and COMPLETED — <name> (early unnumbered items) · SESSION-LOG-<n>. An item is any ## header — a parser that assumes one family will miss twenty items, as one did on 2026-07-28. Archive: closed items live in PENDING-archive.md, original order and numbering preserved. This file carries only what is still open. Numbering is continuous across both files: the next item is one above the highest ## PENDING-<n> in either — a stated number goes stale, a rule does not.

---

PENDING-4 — Bug D: Idle stall + batch embedding during replay (CLOSED 2026-08-03 — done since March; the register never caught up)

Date: 2026-03-22 Tag: [FIX] — reclassified from next-PR to this-PR by steward authorization Summary: Idle state machine transitions during replay freeze async operations. Batch embedding and vector replay skip reduce Phase 1 from 83 hours to ~10 minutes. Files affected: replay-coordinator.ts, bootstrap.ts, ollama-embeddings.ts, vector/index.ts, idle-state-machine.ts Status: Implemented and verified.

CLOSED 2026-08-03 — verified against substrate, not taken from the self-assessment. The **Status:** Implemented and verified. line above is the item's own claim about itself; it was checked rather than believed. Corroborated in BetterMemories.io: betterMemories_app#120 (Phase 2 replay stuck in infinite resource-pause loop) closed, #133 (modules report 'ready' during active replay) closed, plus 03b6a78, 5b14db7, decbdee, and 3332772 (N6, #175 merged) continuing the replay/idle work well past March. Why it stayed open 4½ months: the wake digest recognises (CLOSED)/COMPLETED in a header, not a **Status:** line in a body — so a completed item advertised itself as open every morning.

PENDING-5 — Recall query path returns 0 results (CLOSED 2026-08-03 — instance resolved via GH; the CLASS is still open at #165)

Date: 2026-03-22 Tag: [FIX] Summary: After Phase 1 completes, recall() returns 0 results despite modules reporting ready and vector processing live events. Module dispatch timeouts in query-router. Write path works; read path has separate issue. Rationale: This is the next critical blocker after Phase 1 completion. The query dispatch timeout (2000ms for background latency) may be too short, or facet_id filtering mismatches between observe and recall paths. Files affected: src/core/keystone/query-router.ts, src/core/keystone/query-types.ts, possibly src/modules/vector/queries.ts Awaiting: Investigation — likely needs Seb's input on the query dispatch architecture.

CLOSED 2026-08-03 — the work migrated to GitHub and this register kept a March snapshot. Seb did the investigation through the issue tracker: betterMemories_app#124 (Ollama unavailability silently empties vector query results) closed, #135 (temporal query errors silently return empty results) closed, resolved by bd1f650 feat: typed query status — distinguish 'no results' from 'module failed' — which is precisely this item's symptom ("returns 0 results despite modules reporting ready"). Also c6689eb (recall ranking, #120/#80/#89/#107).

⚠ The instance is closed; the CLASS is not. #165 — H2: silent recall failure on battery is open, priority:critical, production blocker, and is the same failure shape from a different cause: recall returning empty without saying so. Closing PENDING-5 must not read as "silent-empty-recall is solved." Tracked at #165, not here — the register should not hold a second stale copy of an issue GitHub owns.

PENDING-10 — Skip vector embedding during replay (architectural)

Date: 2026-03-22 Tag: [PROPOSAL] Summary: Currently implemented as simple early return in handleEvent. For production: should be a formal replay contract where vector stores content metadata during replay without embedding, then a background re-embed pass populates the HNSW index. Paired with Bug D idle stall fix, this makes Phase 1 fast by design. Awaiting: Steward + Seb architectural review.

Amendment 2026-08-02 — the item's live scope is larger than its 2026-03-22 body, and has been since June. This entry describes a performance proposal (skip embedding during replay, background re-embed). Both parties now use "PENDING-10" to mean something broader: the replay-contract audit question — "does any BMF surface hold state not reconstructible by replay from the logchain?" — framed by the steward in CapableMind-AI/docs/thinking/David/l1-reliability/cover-note-seb-reply-l1-arc-2026-06-06.md ("PENDING-10's replay contract, now with a body of evidence") and its same-day addendum, and echoed by Seb in the 2026-06-07 reply and again in issue CapableMind-ai/betterMemories_app#176 (2026-08-01), which states the audit is blocked on the backup pipeline.

Evidence accumulated since March, none of it recorded here until now: three convergent datapoints from the steward's scan work (Pebbles' independent reinvention of authoritative-log + derived-disposable-index; memory-os and PMB deep-reads showing the fragile class is always a mutable index as primary store; the MemPalace forensic as empirical casualty) — and the concrete trigger, backup.last_success: null on mindfabric-00, meaning the instance holding the steward's accumulated memory has single-copy state whose designed mitigation is precisely logchain rebuildability.

Why this amendment exists. The extension was written in cover notes and never written back into the item. Anyone reading this register — including the wake digest, which surfaces PENDING-10 by its title — got the March scope. Same class as the two record-vs-reality divergences found the same day (the digest's ID-matching bug; a REVIEWED disposition clause read as status): a stable ID whose content has drifted, with no marker that it moved.

Consequence for the split: these are two separable pieces of work and should probably be two items. The performance proposal is architectural and awaits review; the audit question is load-bearing for the provenance story and is now scoped inside Seb's #176 restore drill. Splitting them is the steward's call — flagged, not done.

PENDING-11 — Approve I15 (ICP-9 Pilot Registry Entry: The Accusative Default) (CLOSED 2026-08-03 — REVIEWED-11 AUTHORIZED 2026-03-23)

Date: 2026-03-23 Tag: [PROPOSAL] Summary: Approve I15 as the pilot registry entry, validating both the invariant (The Accusative Default) and the l1_contamination_profile schema field. Full entry drafted in relational-gap-registry-amendment.md §2 since 2026-03-09. Rationale: I15 is architecturally upstream — it defines the system's default relational posture (answerable, not sovereign or neutral). It had the cleanest adversarial performance (promoted Tier 2 → Tier 1). The l1_contamination_profile field carries real content: monotonic pressure from accusative toward authoritative as memory deepens. Approving I15 unblocks: (1) I16 and I17 drafting (Cluster A), (2) schema validation through a real entry, (3) the residual_risk field decision (which can now be made based on evidence from the pilot rather than anticipation). Registry entry location: CapableMind-AI/docs/thinking/David/l2-constitution/amendments/relational-gap-registry-amendment.md §2 Jurist recommendation: YES (from March 8 conversation). Required field for all non-contingent principles. Steward declaration: Steward verbally approved 2026-03-23. Awaiting formal record in REVIEWED.md. Downstream unblocked: I16 (Asymmetry Obligation), I17 (Precedence of Present Expression), Cluster B entries, residual_risk field decision. Files affected: Registry (governance metadata, not code). Awaiting: Steward entry in REVIEWED.md.

CLOSED 2026-08-03 — the entry it awaits has existed since the day it was written. REVIEWED-11 — Approve I15 (ICP-9 Pilot Registry Entry), Date 2026-03-23, Decision AUTHORIZED, ratifying l1_contamination_profile as mandatory for all non-contingent principles and deferring residual_risk pending pilot evidence. The downstream this item lists as blocked was ruled months ago: REVIEWED-15 (I17) and REVIEWED-16 (I16). Registry file verified present.

Why it stayed open 4½ months — two independent defects, either alone sufficient. (1) The REVIEWED-11 and REVIEWED-12 blocks are indented by one space, so every ^## REVIEWED anchor steps over them; a fence-tracked census of REVIEWED.md finds exactly 3 such orphans (these two and REVIEWED-74). (2) Their headers name no PENDING, and resolution is by named item, not by number — so even flush-left they would discharge nothing. Correcting REVIEWED.md is not the executor's to do (Constitutional Constraint #1); flagged for the steward, closed here instead.

PENDING-12 — Lodge Design Notes DN-GOV-01 through DN-GOV-04 (CLOSED 2026-08-03 — REVIEWED-12 AUTHORIZED 2026-03-23; all four files verified present)

Date: 2026-03-23 Tag: [HARDENING] Summary: File four design notes from the Governance Velocity seed brief into l2-constitution/:

• DN-GOV-01: Constitutional Immunity Specification — governance amendment pace decoupled from capability pace. Candidate for new ICP.
• DN-GOV-02: Rate-of-Change as Governance Trigger — external acceleration triggers mandatory constitutional review (not amendment). Constitutional emergency clause analog.
• DN-GOV-03: Baseness Examination Elevation — promote motive examination from practice to formal obligation. System records attestation, not judgment. Requires steward declaration.
• DN-GOV-04: Pace Governor Artifact — structured weekly PENDING.md digest. Pure tooling. Rationale: These emerged from the March 23 jurist conversation on recursive self-improvement and governance velocity. All four address gaps identified when stress-testing L2 governance against I.J. Good's acceleration scenario. Filing as DESIGN NOTE preserves them for cross-strand synthesis without premature constitutional commitment. Files created: DN-GOV-01-constitutional-immunity-specification.md, DN-GOV-02-rate-of-change-governance-trigger.md, DN-GOV-03-baseness-examination-elevation.md, DN-GOV-04-pace-governor-artifact.md Steward authorization: Steward authorized filing 2026-03-23. DN-GOV-03 (baseness elevation) requires separate steward declaration before advancing beyond DESIGN NOTE. DN-GOV-04 (pace governor) is tooling and can iterate without further authorization. Awaiting: Steward entry in REVIEWED.md.

CLOSED 2026-08-03 — ruled the same day, and the series ran on without it. REVIEWED-12 — Lodge Design Notes DN-GOV-01 through DN-GOV-04, Date 2026-03-23, Decision AUTHORIZED ("DN-GOV-03 requires separate declaration before elevation. DN-GOV-04 is tooling, iterate freely"). All four files verified present in CapableMind-AI/docs/thinking/David/l2-constitution/. The series continued far past this item — REVIEWED-13 ruled DN-GOV-05/06/07 and REVIEWED-14 ruled DN-GOV-08 — so the register was reporting a blocked item whose successors had already been decided. Same two-defect cause as PENDING-11 (indented header; names no PENDING).

Still genuinely outstanding from this item, and NOT closed by it: DN-GOV-03's separate steward declaration before it advances beyond DESIGN NOTE. That is a live steward action with no home now that this item is closed — surfaced 2026-08-03 rather than allowed to vanish with the closure.

PENDING — ICP-19 Remit Expansion (Observer Problem)

Date opened: 2026-04-07 Action required: Steward-reviewer conversation with the External Auditor before Observer Problem mechanisms advance to constitutional language. Blocking: OP-03 (mechanism design phase) Notes: Bring OP-02 findings in full. Specifically:

• Fault Line 5 (epistemic diversity question)
• Fault Line 3 (inquiry examining steward with steward's own tools)
• Fault Line 4 (CD-03 Gadamer risk)
• The incommensurability named in OP-CN-01 Status: PENDING — steward to initiate

PENDING — Fault Line 1 Response

Date opened: 2026-04-07 Action required: Steward decision on whether to address PENDING/REVIEWED pipeline gap now or await the External Auditor's input first. Notes: Jurist assessment: most actionable fault line; does not require external review before mechanism design begins. Steward judgment required. Status: PENDING — awaiting steward decision

---

PENDING — ICP-19 Remit Expansion (CLOSED 2026-08-03 — DUPLICATE of the ICP-19 entry above; the live one is retained there)

Duplicate note, 2026-08-03. Same subject, same **Date opened:** 2026-04-07, same requirement (a direct steward–reviewer conversation on remit expansion before Observer Problem mechanisms advance to constitutional language) as ## PENDING — ICP-19 Remit Expansion (Observer Problem) earlier in this file. Two records of one obligation, counted twice by every tally and violating one canonical source of truth per document. The substance is not withdrawn — the prerequisite conversation about the incommensurable foundational positions (OP-CN-01) is preserved in the retained entry, which is the canonical one. Closing the copy, not the obligation.

Title: ICP-19 External Review — Human-Side Governance Scope Date opened: 2026-04-07 Tag: [ESCALATE] Status: PENDING — requires direct steward-reviewer conversation

Summary: The Observer Problem inquiry opens human-side governance questions that the current ICP-19 reviewer remit does not cover. Before any mechanisms proposed through this inquiry advance to constitutional language, the human-side governance question should be explicitly added to the External Auditor's reviewer remit, or addressed by a successor reviewer.

Prerequisite: Direct conversation between steward and reviewer about their incommensurable foundational positions (see Context Note OP-CN-01 §The External Auditor's Comment). This conversation is load-bearing before remit expansion.

Blocking: Constitutional advancement of Observer Problem mechanisms. Not blocking OP-02 synthesis.

---

PENDING — CD-03 Operative (CLOSED 2026-08-03 — bookkeeping only: this is a RECORD of an operative declaration, never an open item)

Bookkeeping note, 2026-08-03. Nothing constitutional is decided or altered here. This entry's own **Status:** reads OPERATIVE — immediate effect, and its **Date authorized:** is 2026-04-07: it is a notification that CD-03 is in force, filed in the register because that is where notifications went. The register's tooling reads every ## PENDING block as an item awaiting authorization, so for four months the wake reported an in-force declaration as an outstanding [CONSTITUTIONAL] decision. Marked closed as a register entry only. The declaration itself is untouched and remains operative at CapableMind-AI/docs/thinking/David/l2-constitution/observer-problem/Constitutional Declaration — CD-03.md — note the path drifted from the one recorded below (observer-problem/ is now under l2-constitution/). CD-03 §IV.4 continues to bind all mechanism proposals.

Title: Constitutional Declaration CD-03 — The Observer Condition and the Limits of Constitutional Architecture Date authorized: 2026-04-07 Tag: [CONSTITUTIONAL] Status: OPERATIVE — immediate effect

Summary: CD-03 reorients the purpose of the architecture from infrastructure-toward-solution to infrastructure-toward-honest-inheritance. The architecture can support the conditions under which the sufficient condition (genuine observer calibration) becomes possible, but cannot produce the sufficient condition itself.

Impact: All subsequent work that proposes mechanisms must be assessed against CD-03 §IV.4: does this mechanism support the conditions, or does it claim to produce the sufficient condition? The latter is a constitutional failure mode.

File: CapableMind-AI/docs/thinking/David/observer-problem/Constitutional Declaration — CD-03.md

---

PENDING-S2 — Hook-aware deposit detection in wake-up (CLOSED 2026-08-03 — obligation rebuilt as [FIX]; never awaited the jurist)

Date: 2026-05-18 Tag: [PROPOSAL] Phase 4 — awaits Jurist contract definition.

Summary: Wake-up detects whether the previous session ended via wrap-up or via Stop hook alone. Surfaces a warning when hook-only: "Previous session ended without wrap-up — pulling thread may be absent or incomplete." Calibrates confidence accordingly.

Rationale: Audit A4 — the strongest single gap in the ligature. A hook-only deposit lacks pulling thread / literal question / pause statement, but currently looks identical to a wrap-up deposit from wake-up's perspective. Jurist (2026-05-18 shape-review): the hooks/skills contract is doctrinal, not tooling. It determines what the unborn session can trust about its inheritance.

Files affected: ~/.claude/skills/wake-up/SKILL.md §2.b.1 + §3.

Awaiting: Jurist shape-review of contract language (candidate text in Jurist shape-review document: "The authoritative deposit is a wrap-up deposit. A hook-only deposit is an emergency fallback, not a complete inheritance. Wake-up must detect which it received and calibrate accordingly."). Then steward authorization.

CLOSED 2026-08-03 — obligation harvested, mechanism rebuilt as [FIX]. The Awaiting line above was wrong for 2½ months: the jurist affirmed Q1 on 2026-05-18 and explicitly assigned the contract to the steward — "CC cannot define what 'authoritative deposit' means — that's constitutional language, and it belongs to you." Nothing was ever awaited from the jurist. Meanwhile the premise died: no Stop hook is configured, and MemPalace — whose mempal_save_hook.sh was the deposit — is retired, steward-ruled 2026-08-03 ("MemPalace is retired and any associated functionality also, except some of the concepts we harvested and implemented in our own way"). The obligation survived its instrument: wake-digest.py computed Last wrap from mtime, so a session ending without /wrap-up left the next wake reporting an older session's thread as current, silently. Rebuilt on our own substrate — the transcripts are the only witness that a session ran. sec_unwrapped() + transcript_span() + wrap_inside(), self-tested with four unit controls and a discrimination check over real sessions (11 wrapped / 2 unwrapped); the warning states what it does not establish. No doctrinal contract required — the mechanism is now ours, not a cross-repo hook. Two real unwrapped sessions found in history: 07-28 06:07, 07-29 16:21.

---

PENDING-S4 — Post-compression marker; cross-repo with mempalace (CLOSED 2026-08-03 — WITHDRAWN with MemPalace; concept kept as a Symmetria §3 flag)

Date: 2026-05-18 Tag: [PROPOSAL] Phase 4 — cross-repo coordination.

Summary: PreCompact hook (~/_Dev/mempalace/hooks/mempal_precompact_hook.sh) writes a marker diary entry (topic: session-compaction) when it fires. Wake-up detects this marker; if present, warns that confidence claims in that session inherit a lossy view. Symmetria adds a post-compression contamination flag (paired with §3 application work in S6).

Rationale: Audit B4 + D4. The PreCompact event currently silent to all downstream consumers; this makes it observable.

Files affected: ~/.claude/skills/wake-up/SKILL.md; ~/.claude/skills/symmetria/SKILL.md §3; ~/_Dev/mempalace/hooks/mempal_precompact_hook.sh (upstream PR or steward-coordinated change).

Awaiting: Jurist contract definition (Q1); steward authorization; mempalace upstream coordination.

WITHDRAWN 2026-08-03 — MemPalace-associated functionality, retired with it (steward ruling: "MemPalace is retired and any associated functionality also"). The marker was to be a MemPalace diary entry written by mempal_precompact_hook.sh; no PreCompact hook is configured, and the diary no longer exists. The concept was harvested rather than lost: post-compression confidence claims are now a standing Symmetria §3 contamination flag ("the working memory was trimmed; what feels certain now may rest on what was lost"), landed with S6 the same day. That is the durable half — a flag needs no hook to fire.

---

PENDING-S5 — Authoritative-diary marker; wrap-up ↔ Stop hook (CLOSED 2026-08-03 — WITHDRAWN; the race it names can no longer occur)

Date: 2026-05-18 Tag: [PROPOSAL] Phase 4 — cross-repo coordination.

Summary: Wrap-up's diary write carries an explicit authoritative: true marker (or AAAK equivalent). Stop hook (~/_Dev/mempalace/hooks/mempal_save_hook.sh) checks for a recent authoritative entry and skips its block if present.

Rationale: Audit C3. Currently a wrap-up + subsequent hook fire may produce two diary entries from different AI states. The second one (post-wrap-up, depleted context) is silently mistaken for the canonical entry by future wake-ups.

Files affected: ~/.claude/skills/wrap-up/SKILL.md §4.b; ~/_Dev/mempalace/hooks/mempal_save_hook.sh.

Awaiting: Jurist contract definition (Q1); steward authorization; mempalace upstream coordination.

WITHDRAWN 2026-08-03 — the race it names can no longer occur. Both parties to the collision are gone: the MemPalace diary (retired 2026-07-07) and the Stop hook that wrote the second entry (mempal_save_hook.sh — not configured; live hooks are SessionStart, UserPromptSubmit, PreToolUse, PostToolUse). With a single writer — /wrap-up writing the session memory file — there is no depleted-context second entry to be mistaken for the canonical one. Withdrawn as discharged by events, not deferred. Distinguished from S2 deliberately: S2's obligation outlived its instrument and was rebuilt; S5's obligation died with the substrate that created it. If a second automated writer of session records is ever introduced, this item is the precedent to re-open.

---

PENDING-S6 — Symmetria §3 contamination flag applications of the Directive elaboration (CLOSED 2026-08-03 — IMPLEMENTED)

Date: 2026-05-18 Tag: [HARDENING] Phase 3b — depends on S0 (now CLOSED).

Summary: Extend ~/.claude/skills/symmetria/SKILL.md §3 contamination flag list with applications of the now-constitutional time-the-task-requires principle, plus three other self-flags surfaced by the audit:

• Lectio (corpus reading): take the time the corpus asks for.
• Diagnose-don't-fix (debugging): trace the class of failure before patching the instance.
• Dwell-on-composition (writing): the recommendation gets the time it wants, not the time the executor wants the recommendation to take.
• Alignment pulse returning aligned without naming a specific tension — premature-closure (D1).
• Search queries shaped by what the session wants to find rather than what it needs to find (D5).
• Post-compression confidence claims — the working memory was trimmed; what's certain now may rest on what was lost (D4; pairs with S4).

Rationale: Audit D1/D4/D5 + the principle elevation. §3 currently flags external code and writing patterns; with the Directive elaboration in place, applications of it at the discipline level are coherent additions, not scope-creep.

Files affected: ~/.claude/skills/symmetria/SKILL.md §3.

Awaiting: Steward authorization (S0 closure unblocks).

IMPLEMENTED 2026-08-03 — ~/.claude/skills/symmetria/SKILL.md §3. All six flags landed: the three time-the-task-requires applications (lectio · diagnose-don't-fix · dwell-on-composition) grouped as one entry under the now-constitutional Q4 elaboration, plus premature-closure-pulse (D1), query-shaped-by-what-it-wants-to-find (D5), and post-compression-confidence (D4). D4 is retained on its own merit though S4 was withdrawn the same day — compaction still occurs; only the MemPalace marker died. Unblocked since Q4 landed in ~/CLAUDE.md; the delay was bookkeeping, not dependency.

---

PENDING-S7 — Symmetria check mode: add suspend outcome (CLOSED 2026-08-03 — IMPLEMENTED; Q5 was affirmed 2026-05-18)

Date: 2026-05-18 Tag: [HARDENING] Phase 5.

Summary: §6 check mode outcomes extend from proceed / return-and-reframe / escalate to proceed / return-and-reframe / suspend / escalate. suspend = hold for unhurried steward judgment without urgency.

Rationale: Audit D3 + Jurist confirmation. Today's audit was the missing-shape example: neither escalate (urgent) nor return-and-reframe (the audit is the right work) fit. With the Directive elaboration in place, suspend is the natural outcome — the time the steward's judgment requires is task-time, not interruption-time.

Files affected: ~/.claude/skills/symmetria/SKILL.md §6 (check).

Awaiting: Steward authorization.

IMPLEMENTED 2026-08-03 — ~/.claude/skills/symmetria/SKILL.md §6 now reads proceed | return-and-reframe | suspend | escalate, with suspend defined against its two neighbours (not escalate, which carries urgency; not return-and-reframe, which says the work is wrong) and required to name what is suspended and what would resume it. The header's "awaiting Q5" was stale: Q5 was affirmed 2026-05-18 ("Yes, add it"), conditional only on Q4, which has since landed. Used in this session before it was written — the hold on CONTROL-A v2 is a suspend, not an escalate.

---

PENDING-S9 — Wrap-up §8 output template enriched to match practice (CLOSED 2026-08-03 — IMPLEMENTED; Q2/Q3 were affirmed 2026-05-18)

Date: 2026-05-18 Tag: [HARDENING] Phase 5 — depends on Q2 + Q3 (Q3 confirmed by Jurist).

Summary: §8 output template in wrap-up expanded to mirror the three-tense richness the steward already produces in session memory files: Past / Present / Future as named sections, with required fields under each. Subsumes S1 if implemented together; or S1 lands first as smaller increment and S9 follows as deeper revision.

Rationale: Audit C5 diagnostic — template under-specifies what good practice already does. With the Directive elaboration in place, an output template that drops the practice's load-bearing tenses under compression is itself an instance of the failure mode the principle catches.

Files affected: ~/.claude/skills/wrap-up/SKILL.md §8.

Awaiting: Steward authorization. Optional relationship to S1: implement S1 first (minimal additive), then S9 as deeper revision; or fold S1 into S9 as single revision.

IMPLEMENTED 2026-08-03 — ~/.claude/skills/wrap-up/SKILL.md §8 restructured into the three tenses. S1 had already landed (archived), so this is the deeper revision on top of it. The diagnosis was exact and sharper than the item stated: Future was already well-specified — pulling thread, resumption point, literal question, and Q3's constitutive pause statement were all present — while Past and Present were wholly absent. Added: what-happened / what-held / what-was-corrected (Past) and the-mood / confidence-to-recalibrate (Present), with deferred-decisions and skill-harvest relocated under Present. Future deliberately still leads, inverting the memory file's narrative order: the steward reads this at departure, but it is written for arrival. Q2 was affirmed 2026-05-18 and Q3 elevated to constitutive the same day; both had landed. Every pre-existing field survives — none dropped.

---

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.

PENDING-79 — CLAUDE.md doctrine preservation: §MemPalace retargeted, two rules hoisted (extraction legs A + B)

Date: 2026-07-28 Tag: [ESCALATE] — edits doctrine in ~/CLAUDE.md (Constitutional Constraint #1). Executor drafts; steward applies. Summary: The "two deletions and a pointer" estimate was wrong. A weld test at bullet/row granularity found 11 of 15 editable units across §MemPalace and §Active Projects carry doctrine, three with no standing carrier anywhere else — including L130, which yesterday's eval credited as one of three carriers of the false-premise guardrail. Deletion would excise live doctrine. Legs A and B preserve it; the deletions (leg C) become safe only afterwards.

Rationale. The remedy is right and the price was wrong, for a nameable reason: both this proposal and the withdrawn PENDING-76 amendment priced a decomposition as a relocation. If the correct partition is by cadence and the text is organized by topic, extraction is a rewrite, not a move. Steward decision 2026-07-28: preserve the doctrine.

Weld census (verified against substrate, line granularity):

• §MemPalace L115–132 — 8 units, 7 carry doctrine; only the tool roster (L122) deletes clean.
• §Active Projects L237–248 — 7 units, 2 carry doctrine (the read-local-CLAUDE.md rule L246; the Compass read-only constraint, riding inside a state row).
• No standing duplicate carrier exists for: L120 (Wrong is worse than slow), L130 (the conflict rule), L246. Other hits are session narratives recording the decision, not instructions. L246's only second carrier is Symmetria §3 — invoked, not standing.

Leg A — replace §MemPalace with §Memory Discipline

Anchored edit (not line-numbered — anchors survive reordering). Replace from the heading ### MemPalace as Primary Memory through the line Storage is not memory. Memory is storage exercised by protocol. inclusive (currently L115–132, 18 lines) with:

### Memory Discipline

  Storage is not memory. Memory is storage exercised by protocol.

  The durable substrate is the files layer: git-tracked Markdown and JSONL, entered through
  `MEMORY.md` (loaded at wake), with `~/PENDING.md` and `~/REVIEWED.md` as the governance record.
  Instruments for reaching it change; the obligations below do not — state the obligation first
  and the instrument second, or the next retired tool takes a rule down with it.

  - **Before claiming any fact** about people, projects, or past events that isn't in immediate
  context: check first. Wrong is worse than slow.
  - **"Let me check"** — when the answer matters and isn't immediate, say so and check. The
  cheapness of checking is the point.
  - **When facts change, supersede explicitly** — mark the superseded record as superseded and
  write the new one. An unmarked correction leaves two live versions and no way to tell which is
  current.
  - **Save what's worth keeping** — the wrap protocol writes the session record; if something
  load-bearing surfaces mid-session, write it then. Automation assumed to fire is not a record.
  - **A conflict between two memory layers is a verification trigger, not a precedence call** —
  neither layer wins automatically. Every layer is a point-in-time snapshot of something else;
  continuous maintenance buys currency, not authority, and carries its own silent-drift classes.
  On conflict: verify against the **primary substrate** — the code, the git history, the document
  itself — before acting, then correct whichever layer was wrong. Treat every memory layer as
  witness, not notary.

What leg A preserves, unit by unit: storage-is-not-memory (verbatim) · before-claiming + Wrong is worse than slow (verbatim) · Let me check (verbatim stance) · supersede-explicitly (generalized off kg_invalidate/kg_add, with the reason added) · save-what's-worth-keeping (fallback obligation kept; the false hook claim becomes the rule its own falsity earned) · the conflict rule incl. witness, not notary (generalized from MemPalace-vs-files to any two layers; the operative clause — verify against the primary substrate before acting — is unchanged).

What leg A drops: the tool roster (8 unresolvable tool names) and the hook mechanism claim (Stop/PreCompact unconfigured) — both verified false by governance-drift-check.py.

Two changes that are not pure preservation — flagged, not smuggled:

1. Addition. The lead-in's closing clause — "state the obligation first and the instrument second, or the next retired tool takes a rule down with it" — is new doctrine, not preserved doctrine. It is the rule whose absence produced this entire drift. Strikeable without affecting anything else in leg A.
2. De-duplication. The original states the storage/protocol maxim twice (lead-in and closing line). The draft states it once, as the opener.

Leg B — hoist two rules out of §Active Projects

Append to ### Session Discipline (after its last bullet, If session state is growing large…). Plain, unbolded, no terminal periods — matching that section's style, not §Context Rot Prevention's:

- When entering a project directory, read its local `CLAUDE.md` first — current state, build sequences, terminology — before acting in the repo
- The Compass vault (`~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass`) is the steward's personal operating system: reference it, never write to it

Both paths verified to exist 2026-07-28 with positive controls. Equal-force hoist: the Compass constraint had the force of a table note and keeps it. It could instead be folded into Constitutional Constraint #3 (Territory respect) — that is a strengthening, not a preservation move, so it is offered as an option and not recommended here.

Verification (checkable, both directions): after A + B, python3 ~/dotfiles/scripts/governance-drift-check.py must report exactly 7 — down from 9 — and must specifically no longer report L122 (tool names) or L126 (hooks). Any other count means the edit did not land as drafted. Predicted full sequence: A+B → 7 · terminal-newline fix → 6 · leg C → 0.

Sequencing — one dependency dissolves. PENDING-77's five structural defects: L241, L242, L243, L248 all sit inside the region leg C deletes; only L258 (missing terminal newline) survives it, and that one must precede any line-referenced patch regardless. Recommend narrowing PENDING-77 to its single newline fix; the other four dissolve rather than get solved.

Options:

• (i) Apply A + B as drafted — doctrine preserved, both false claims cleared, §Active Projects left as pure state ready for leg C.
• (ii) Apply A + B with the addition struck — pure preservation, no new doctrine.
• (iii) Defer — but note the file currently asserts eight tool names and two hooks that do not exist, which is Constitutional Constraint #4 (honest degradation) failing in the document that states it.

Recommendation: (i). The addition costs one clause and is the only thing in the change that prevents recurrence; the rest is faithful preservation. Each leg is complete in itself — if leg C never lands, A + B still leave the file honest.

Files affected: ~/dotfiles/CLAUDE.md (steward applies). Executor modifies nothing under ~/CLAUDE.md. What is NOT changed: the §Active Projects table rows (leg C, separate item) · §Constitutional Constraints · ~/REVIEWED.md · the L43–61 executor-agency block (separate, still resting on a partly withdrawn finding). Awaiting: Steward authorization.

PENDING-80 — Doctrine IDs: annotate the canonical, never extract it (pilot on §Memory Discipline)

Date: 2026-07-28 Tag: [ESCALATE] — edits ~/CLAUDE.md (Constitutional Constraint #1). Executor drafts; steward applies. Summary: Give each doctrine unit a stable machine-readable id in an HTML comment, inside the canonical. Pilot scope: the seven units of §Memory Discipline, which PENDING-79 leg A has just rewritten. No prose changes — ids only.

Rationale — why annotation and not a machine-readable sidecar. The chamber pairs a human-readable canonical with a .meta.json sidecar because a chamber canonical is a fixed historical text we may not touch; its machine layer has nowhere to live but outside it. ~/CLAUDE.md is a living document we author, so that constraint does not apply and the sidecar pattern inverts: the machine layer belongs inside. This matters for three reasons:

1. L110. A derived governance file is a parallel version. An in-place annotation is not.
2. Authority inversion. If the executor consumed a derived layer while the steward authored the prose, what governs would be the extractor's output, not the steward's text — PENDING-78's "two parties holding different maps," made structural and permanent.
3. Doctrine does not separate from state cleanly, and we have three demonstrations from one morning. The PENDING-76 amendment mislocated the seam at the claim level; the executor's own section-level census mislocated it again; drafting then caught a third error (L126) an hour after it was published as fact. An automated extractor makes that error silently and every time.

Convention:

• Form <!-- D:<section>.<slug> -->, lowercase, hyphenated, one dot. Invisible in rendered prose.
• Placed at the end of the unit's final line. One id per editable unit (bullet, aphorism, or paragraph).
• An id names an obligation, never an instrument — so a retired tool costs a word, not an id.
• Renaming an id is a breaking change: any skill citing it must be updated in the same commit.

Draft — the seven units as currently applied, ids appended, prose untouched:

  Storage is not memory. Memory is storage exercised by protocol. <!-- D:memory.storage-is-not-memory -->

  The durable substrate is the files layer: git-tracked Markdown and JSONL, entered through
  `MEMORY.md` (loaded at wake), with `~/PENDING.md` and `~/REVIEWED.md` as the governance record.
  Instruments for reaching it change; the obligations below do not — state the obligation first
  and the instrument second, or the next retired tool takes a rule down with it. <!-- D:memory.obligation-before-instrument -->

  - **Before claiming any fact** about people, projects, or past events that isn't in immediate
  context: check first. Wrong is worse than slow. <!-- D:memory.check-before-claiming -->
  - **"Let me check"** — when the answer matters and isn't immediate, say so and check. The
  cheapness of checking is the point. <!-- D:memory.say-you-are-checking -->
  - **When facts change, supersede explicitly** — mark the superseded record as superseded and
  write the new one. An unmarked correction leaves two live versions and no way to tell which is
  current. <!-- D:memory.supersede-explicitly -->
  - **Save what's worth keeping** — the wrap protocol writes the session record; if something
  load-bearing surfaces mid-session, write it then. Automation assumed to fire is not a record. <!-- D:memory.write-when-you-see-it -->
  - **A conflict between two memory layers is a verification trigger, not a precedence call** —
  neither layer wins automatically. Every layer is a point-in-time snapshot of something else;
  continuous maintenance buys currency, not authority, and carries its own silent-drift classes.
  On conflict: verify against the **primary substrate** — the code, the git history, the document
  itself — before acting, then correct whichever layer was wrong. Treat every memory layer as
  witness, not notary. <!-- D:memory.conflict-is-verification-trigger -->

The enforcement is already built and dormant. governance-drift-check.py gained a section 6 (2026-07-28) that parses ids from ~/CLAUDE.md, scans ~/.claude/skills/**/*.md for citations, and reports duplicate ids and citations to ids the canonical does not define. It deliberately does not scan PENDING.md, where drafts legitimately quote ids that do not exist yet. It is silent today because no ids exist, and it carries four same-run controls plus a synthetic proof (a fabricated duplicate and a fabricated dead citation were both detected) — so a future "nothing reported" means checked and clean, not never looked.

What this does NOT do: it does not extract, summarise, or duplicate any doctrine; it does not change a single word of prose; it does not touch any section other than §Memory Discipline; it creates no new file.

Verification: after applying, governance-drift-check.py must still report 7 — ids add no findings — and section 6 must move from dormant to active with 7 ids defined, 0 dead citations.

Follow-on, genuinely blocked (dependency named): having skills cite D: ids instead of paraphrasing doctrine cannot start until the ids exist in the canonical, i.e. until this item is applied. /wake-up, /wrap-up and /symmetria each paraphrase rules that would become citations.

Options: (i) apply as drafted · (ii) apply with different id names · (iii) reject — in which case section 6 should be removed from the drift check rather than left as dead code. Recommendation: (i). Files affected: ~/dotfiles/CLAUDE.md (steward applies). Already landed without authorization, being detection-only: ~/dotfiles/scripts/governance-drift-check.py §6. Awaiting: Steward authorization.

PENDING-81 — Keeping CLAUDE.md and the Claude.app preferences fresh with respect to each other

Date: 2026-07-28 Tag: [ESCALATE] — steward-held document, and one finding touches the party structure itself. Summary: The two governance documents cannot be kept in sync by the same mechanism, because their readers differ in one decisive way. Extends PENDING-78 with findings only possible now that the executor has seen the preferences' text.

The structural fact that determines everything else. ~/CLAUDE.md is read by an executor with filesystem access, so its state can be computed — which is why governance-drift-check.py works and why leg C could replace §Active Projects with a pointer. The .app preferences are read by a jurist with no filesystem access. Their state therefore cannot be computed at read time; it can only be cached. Confirmed by substrate: the live preferences are not on disk in any readable form — the only hits are March-era snapshots under ~/Library/Application Support/Claude/local-agent-mode-sessions/. No instrument here can ever check them. So the goal is not "make them derived." It is: keep the cache small, generate it, date it, and track its age.

Findings (new, from reading the preferences text):

1. ⚑ The two documents disagree on the party structure. CLAUDE.md L88–90 names three parties: David / Claude.app / Claude Code. §Your Role names Cowork as a fourth with its own governance document COWORK.md, while calling the model three-party. COWORK.md is real but orphaned — # COWORK.md — Global Instructions, dated Mar 22, inside an agent-mode session sandbox. This is doctrine welded to a retired instrument, the same shape as the MemPalace weld, but at the constitutional layer. Needs a ruling, not a refresh: is Cowork still a party?
2. The jurist's map is inverted relative to the substrate. §Standing Context names L1 as active development. Commits in the last 30 days: chamber-library 165, studium-engine 25, CapableMind-AI 5, BetterMemories.io 0, ARC 0. The two highest-activity workstreams appear nowhere; Be is absent entirely. The Chamber is named in §Who I Am as a thing the steward designed, giving no signal that it is the live work.
3. ARC "near-operational" understates it in a misleading direction — Stage G sealed 2026-06-10, and its 0 commits/30d mean finished and quiet, not nearly ready.
4. "Divorce: Settled, awaiting signing March 30, 2026" — that date is four months past. Steward-held and unverifiable from here; flagged only because "awaiting" a past date reads as current.
5. Confirmed from PENDING-78: the fix/replay-durability-contracts branch pointer (merged; HEAD is main) and "L2 blocked pending L1 stability" (L1 dormant 30 days).

The good news: the document is already correctly tiered. §Who I Am, §Your Role, §Intellectual Operating System, §How We Work Together and §Communication are doctrine and identity — they do not drift. Every finding above except #1 sits in §Standing Context. So the fix is small: one section gets a cadence.

Proposed mechanism:

• Split §Standing Context into ### Standing Context — Projects (generated, dated, replaced wholesale) and ### Standing Context — Personal (hand-held).
• Generate the first with python3 ~/dotfiles/scripts/wake-digest.py --brief (built 2026-07-28): tracker index, open authorization items, last rulings, 30-day commit counts per repo, drift count, and an explicit generated <date> header instructing the reader to treat it as unverified after ~30 days. ~1k tokens.
• Never generated: the orchestra conflict, fraternal practice, and family/legal entries. They are steward-held, unverifiable from any substrate, and the generator is scoped to exclude them by design, not by convention.
• The wake reports the brief's age when it exceeds 30 days, and says plainly that it tracks generation, not pasting — a lower bound on the jurist's staleness, never a guarantee of freshness. This is the honest limit of what can be instrumented across a boundary we cannot read.

Why this beats the alternative. A pointer ("see ~/CLAUDE.md") is useless to a reader who cannot open files — which is precisely why the preferences accumulated duplicated state in the first place. The duplication is structurally required; only its staleness is optional.

Files affected: Claude.app personal preferences (steward edits). Already landed, detection/generation only: ~/dotfiles/scripts/wake-digest.py --brief. Awaiting: Steward decision on finding #1 (is Cowork a party?), and authorization for the §Standing Context split.

PENDING-82 — Read-only MCP server: giving the jurist eyes on the substrate

Date: 2026-07-28 Tag: [PROPOSAL] — new interface between two governing parties. Built and self-tested; not installed. Installing it edits the steward's desktop-app config. Summary: ~/dotfiles/scripts/governance-mcp.py publishes the governance substrate to Claude.app's chat surface as five read-only tools, closing the gap PENDING-81 could only narrow. Supersedes PENDING-81's premise that a generated cache is the best available answer — for chat, it is no longer the only one.

The gate PENDING-81 left open is answered, and my framing of it was backwards. Steward-confirmed 2026-07-28: local MCP servers configured in claude_desktop_config.json are exposed to the chat surface, and have been since roughly a year before Cowork existed — never Cowork-gated. Cowork gets them conditionally: local sessions inherit them, remote sessions — now the default execution mode being rolled out — do not run local MCP at all. So the relationship is not "chat, not only Cowork" but "chat, always; Cowork, only while it still runs locally." The jurist chat sits on the stable side of that split, which makes this design less exposed to product drift than the Cowork-dependent one considered and rejected on 2026-07-28.

Substrate check: claude_desktop_config.json has no mcpServers key (top-level keys: coworkUserFilesPath, preferences). Its preferences block is app UI state — sidebar mode, pinned panes, Cowork toggles — not the jurist's Standing Context prose. Name collision only; PENDING-81's finding that the live preferences are nowhere on disk stands unrevised.

What it exposes (five tools, all read-only):

• governance_state — every open item with its [TAG], recent rulings, drift count, per-repo status. Computed per call.
• governance_item(id) — the verbatim body of any item or ruling, across PENDING.md, PENDING-archive.md, REVIEWED.md. This is the capability a pasted cache can never have: the jurist can read the thing it is ruling on.
• governance_read(file, offset, limit) — verbatim paged read of one of six enumerated documents.
• drift_report() — full governance-drift-check.py output.
• repo_activity(repo, count) — branch, dirty count, recent commits.

Four refusals designed in, each with a control that proves the refusal detectable:

1. Read-only. No tool writes. Audited by AST, not by text search: 0 filesystem-mutating calls, git subcommands present = {log, status} only. A write path would collapse three parties into one.
2. Not an agent. Tools return data, verbatim where possible. The rejected alternative — a second Claude with filesystem access reporting back — yields an agent's testimony about the substrate, not the substrate.
3. No second parser. "An item" is defined once, in wake-digest.py's item_spans(), imported here. A private second definition is how twenty items went missing on 2026-07-28.
4. No path arguments. Every tool takes a key from a fixed enum. There is no traversal to defend because no path is accepted; the reachable domain is enumerable rather than defined by the instrument.

Verified: 29 self-test controls pass, 0 fail (governance-mcp.py --selftest; counted from the run, not estimated — the first draft of this line said 27). Each absence is paired with a same-run positive control (Q2). wake-digest.py --selftest holds at 19. Plus a live stdio round-trip — initialize → notifications/initialized (correctly unanswered) → tools/list → two tools/call → malformed input survived as a -32700 rather than a crash; stdout carried only JSON-RPC, stderr empty.

[FIX] applied to the shared definition while here. item_spans() is now fence-aware: a ## header inside a fenced code block is neither an item nor an item boundary. Zero such headers exist in the substrate today, so behaviour is unchanged (17 open items before and after) — but governance drafts are written as fenced markdown carrying ## REVIEWED-N headers, per the steward's own copy-paste-clean practice, so the next such draft would have created a phantom item and truncated the real item containing it. Latent defect with a live trigger, not a hypothetical.

⚑ A false pointer in yesterday's own resumption point. It stated the two §Your Role edits were "drafted verbatim in the transcript and in PENDING-81." They are not in PENDING-81; they existed only in a transcript discarded at the restart. Same wrap that mis-stated the archive. The lesson is the one already in doctrine: a draft that lives in a transcript is not a record. Re-drafted below, in the file this time.

Installation (steward's hand — it edits the app's config, and the app must restart):

{
  "mcpServers": {
    "governance": {
      "command": "python3",
      "args": ["/Users/davidglidden/dotfiles/scripts/governance-mcp.py"]
    }
  }
}

Merge that mcpServers key into ~/Library/Application Support/Claude/claude_desktop_config.json alongside the existing coworkUserFilesPath and preferences keys, then restart Claude.app. Reversal is deleting the key.

Cowork retirement — §Your Role replacement text (re-drafted; the steward places it, since the surrounding prose is not readable from here):

Three parties hold distinct roles: steward (David) authorizes; jurist (Claude.app) proposes and governs; executor (Claude Code) implements within authorization.

Delete the Cowork party entry and every reference to COWORK.md. Grounds, now two: a third executor costs a third doctrine copy of a document that is CLAUDE.md with the nouns changed; and Cowork could not have served as the jurist's filesystem eyes even in principle, since coworkUserFilesPath points at ~/Claude, which does not exist, and remote Cowork — the incoming default — runs no local MCP at all.

Files affected: new ~/dotfiles/scripts/governance-mcp.py; ~/dotfiles/scripts/wake-digest.py (item_spans() fence-awareness + 3 controls). Awaiting steward hand: claude_desktop_config.json, Claude.app §Your Role and §Standing Context. Awaiting: Steward authorization to install the mcpServers key. The server itself is inert until then — nothing loads it.

PENDING-83 — The evidence tier is decided by file extension, so a born-digital PDF gets a false ABSTAIN

Date: 2026-07-28 Tag: [PROPOSAL] Summary: verify_body_conservation.tier_of() classifies by suffix — .pdf → V-SCAN → the body-conservation gate ABSTAINS and the candidate proceeds unverified — but every PDF-sourced canonical tested has a real text layer, so ground truth exists and the strongest available check is being skipped on the grounds that it is impossible.

Rationale. Surfaced by the Harrison re-gate pilot, at its first gate question, before any conversion ran. tier_of() (scripts/verify_body_conservation.py:457-467) reads the source's extension only: .epub/.azw3/.mobi → V-TEXT, .pdf → V-SCAN, else V-UNKNOWN. V-SCAN abstains by design, and the spec is explicit that this abstention is the permanent, tier-level kind — "this tier has NO ground truth" — which proceeds, unlike the contingent run-level UNVERIFIED, which holds.

The premise is false for this source and, on the evidence, for the class. the-dominion-of-the-dead-harrison.pdf (banked, sha 06f0158a…, match_cov 1.0) carries four embedded Type-1C subset fonts and yields 1,549 words from pages 1-12 via pdftotext. It is a typeset born-digital PDF, not a scan. The landed canonical was itself produced by pdftotext + python, and the 2026-07-28 Docling trial measured 90,155 words against a 90,955-word source extraction — 99.1%. Ground truth not only exists, it has already been used to measure this exact file twice.

Consequence for the pilot: Harrison — chosen because it is the known-worst apparatus case, to exercise the mechanism where it is most likely to break — would graduate with no verbatim verification performed, and the gate would report an honest-looking abstention while doing so. Per the jurist's 2026-07-14 ruling (PENDING-55 res.a): "A false ABSTAIN is as much a lie as a false PASS." This is also the fifth-instance shape v2.7.0 named — a reported non-failure where no verification occurred.

Grounding — this is arguably a conformance gap against already-ratified text, not a new direction. Spec v2.7.0 (§Tiering & Fence evidence-tiers preamble, REVIEWED-75) ratified that verification method is declared for the work's kind, with an anti-bypass guard bound to the property, not enrollment — no work may weaken its applicable method by re-labelling. tier_of() binds the method to a label (the filename suffix), which is precisely the coupling that clause forbids. A born-digital PDF is not a different kind from a born-digital EPUB with respect to the property that matters — extractable ground-truth text — and the extension is doing the re-labelling automatically.

Exposure — bounded measurement, stated as such. 6 canonicals declare source_format: pdf; 5 fell within the read-slice I sampled and all 5 resolve to banked PDFs with a text layer (born-digital 5 · scan-like 0). One file is unaccounted for by my slice. This is a sample, not a census — a full census over the corpus is a separate measurement and is not claimed here. On the sample, the V-SCAN tier presently contains no scans at all.

Options.

• (a) Probe the property, not the extension. tier_of gains a decidable text-layer probe for .pdf: extractable text above a declared threshold → V-TEXT; below → V-SCAN. Threshold and probe live in graduation-spec.yaml as declared data (the house requirement/mechanism split). Mechanically decidable, carries its own positive and negative control, and applies the v2.7.0 property-not-label guard to the one place it was not applied.
• (b) Per-file declared tier. An attested evidence_tier: in frontmatter or the sidecar, attest-never-default. Honest, but pushes judgment onto a curator for something a probe can decide, and adds an attestation surface to every PDF.
• (c) Narrow the change to the pilot. Re-tier Harrison alone by hand and leave the classifier. Rejected on its face: it fixes the instance and leaves the class, which the executor directives forbid.

Recommendation: (a). It is the only option that binds the method to the property the spec already says it must bind to; it is mechanically decidable rather than curator-judged; and its discriminator is already demonstrated on real material (the pdffonts + pdftotext probe run above, which correctly separates a typeset PDF from a scan and would return the opposite verdict on a scan). Per v2.7.0's extension path, a method must be demonstrated on real material before ratification — that demonstration is the natural first deliverable if authorized, and it should include a true scan as the negative control, which the corpus does not presently appear to contain and may need to be supplied.

Change class. PROPOSAL, not FIX: it changes what the gate accepts (a class of candidates moves from abstain-and-proceed to verified-or-held). The amendment discipline is explicit that this crossing is what makes a change PROPOSAL-class, even where the change restores conformance with ratified text.

What this does NOT block. Harrison's reconversion, cleaning, strip_cruft/verify_conversion, the running-head handling, the boundary-drop attestation, and the voice-purity reading pass are all unaffected and proceed. What is blocked is the final graduation stamp, which would otherwise land on an unverified file.

Files affected: scripts/verify_body_conservation.py (tier_of, + controls in test_tools.py); _curation/graduation-spec.yaml (body_conservation: — probe + threshold as declared data). No canonical, no hash, no binding touched by this item. Awaiting: Steward authorization. Harrison holds at the graduation stamp until ruled; every prior step proceeds.

PENDING-83 — ADDENDUM 1 (2026-07-28, same session, before any ruling): the recommendation is corrected to a distinct V-DPDF tier

Superseding my own Recommendation (a) above, on the steward's correction. The original item proposed probing the property and re-tiering born-digital PDFs — with V-TEXT as the implied destination. That destination is wrong, and the item should not be ruled on as written.

Why V-TEXT cannot receive them. The V-TEXT criterion is not merely a policy that could be pointed at a new format; its ratified reference conversion is pandoc -f epub -t markdown-smart — source-anchored AND writer-matched (REVIEWED-72, graduation-spec.yaml body_conservation.reference_writer). There is no -f epub for a PDF. Routing PDFs into V-TEXT would inherit a criterion whose reference cannot be produced for the substrate, which is precisely the failure this repo already has a named lesson for: "a check proven for one tier is NOT proven for another (V-DSL ≠ V-TEXT — the k-gram check false-flagged the DSL's reflow) — demonstrate per case, don't reuse-and-assume." I reached for the nearest existing tier without asking whether its method transfers. It does not.

Why a distinct tier is the right shape, on the ratified test. v2.7.0 holds that verification method is declared for the work's kind. A born-digital PDF differs from a born-digital EPUB in the property that decides the method: an EPUB carries an explicit reading order and reflowable structure, while a PDF's reading order is inferred from page layout. That is not a smaller version of the same problem — it is the layer-2 PASS-BUT-FALSELY case §VII already names (column reassembly across a gutter: same words, wrong order, invisible to any word-guard). It also brings hyphenation at line breaks and running heads interleaved into the text stream — the running-head defect already blocking this very pilot. Same property (ground truth exists), different kind (how ground truth is recovered, and what can go wrong recovering it). Two tiers, two declared methods.

Revised recommendation: add V-DPDF as a declared kind with its own method, entering by v2.7.0's extension path (new kind by PROPOSAL, method demonstrated on real material before ratification). tier_of() stops deciding by suffix and dispatches on a structural probe: .pdf → V-DPDF if born-digital, V-SCAN if scanned. The deterministic/scan split v2.7.0 preserved is thereby preserved and extended, not flattened.

On self-declaration — the steward's question, answered plainly: a PDF cannot reliably declare its own origin. There is no standard "I am a scan" flag. /Producer and /Creator are self-report — frequently absent, frequently wrong (a scan re-saved through Acrobat reports Acrobat), and overwritten by any post-processing. PDF/A conformance declares archival intent, not origin. Metadata is testimony; structure is evidence — the same distinction this corpus already applies to every other attestation. But the structure IS decidable, on a triad: extractable text density on interior pages · embedded text fonts · page-sized image coverage per page. Born-digital = text drawn, fonts embedded, no page-sized image. Scanned-with-OCR = text over one page-sized image per page. Bare scan = no usable text.

Demonstration status. A read-only classifier implementing that triad is built and self-tested in scratchpad (classify_pdf_origin.py, 8 controls incl. a live end-to-end); it is deliberately NOT a fleet tool and NOT wired to any gate — it exists to produce the evidence v2.7.0 requires before ratification. Its own first version failed its live control, classifying a 68-font typeset Harrison as inconclusive at 42.7 words/page: it sampled pages 1-8, which are half-title, title, copyright and contents. Corrected to sample the interior, the same file reads 397.6 words/page — a 9x error caused purely by the measurement window, and caught only because the control ran against a known answer. That failure is itself an argument for this item: an instrument that samples the wrong region reports a confident wrong verdict, exactly as tier_of() does.

Still owed before ratification: a true scan as the negative control. A classifier that has only ever returned born-digital has not been shown capable of returning scanned. A corpus-wide census over the master library (385 PDFs) is running to find one; if the corpus contains no genuine scan, that is itself a finding — and the control must then be supplied deliberately rather than assumed. Awaiting: Steward authorization, on the revised V-DPDF shape rather than the original recommendation (a).

PENDING-83 — ADDENDUM 2 (2026-07-28, same session, before any ruling): the exposure figure in the original item is WRONG and is retracted

Retracting my own measurement. The original item reported: "6 canonicals declare source_format: pdf; 5 fell within the read-slice and all 5 resolve to banked PDFs with a text layer (born-digital 5 · scan-like 0) … On the sample, the V-SCAN tier presently contains no scans at all." That is false. Do not rule on it.

How it was wrong, twice over. (1) The probe sampled pages 1-10 and thresholded on raw word count — pages 1-10 of a typeset book are front matter, so it measured half-title and contents pages and generalised to the book. The same defect later made the corrected classifier's first version call a 68-font Harrison inconclusive at 42.7 words/page against its true interior 397.6. (2) It enumerated candidates by grepping source_format: pdf in frontmatter, which is a declaration, not the resolved source. juvenescence-harrison declares nothing useful here: its banked source is an .epub, and the PDF I found bearing that title was a master-library copy, not the canonical source. The standing invariant already says this — a canonical's source is whatever resolve_archived_source returns, never a path in frontmatter, never the master library — and I violated it while writing an item about verification.

The corrected census, by mechanism (resolve every canonical's source, then classify the ones that are PDFs):

resolved-PDF canonicals	count
scanned-with-OCR	35
bare-scan	9
born-digital	16
total	60

44 of 60 (73%) are genuine scans. The steward stated this from direct knowledge of the library before the measurement returned; the measurement agrees with him.

This strengthens the proposal rather than weakening it, and changes its shape. V-SCAN is not a vestigial or empty tier to be corrected away — it is correct for 44 canonicals and must keep its abstention, exactly as v2.7.0's preserved deterministic/scan split requires. The defect is narrower and sharper than I first stated: 16 canonicals whose sources carry real ground truth are being abstained on as though they carried none. That is the false-ABSTAIN population, and it includes the pilot's own book. Same author, same subtradition folder, opposite tiers: the-dominion-of-the-dead-harrison is born-digital (68 fonts, no page image) while forests-shadow-of-civilization-harrison is scanned-with-OCR (805 fonts, one page-sized image per page). Neither the author, the collection, nor the folder can decide the tier — only the file's own structure can, which is the argument for a structural probe stated as a demonstrated fact rather than a prediction.

Two further findings, surfaced not resolved.

• 9 bare-scans (e.g. mal-darchive, on-textual-understanding-szondi) have zero extractable text — 0 fonts, 0 words per page. Their canonicals exist, so text was obtained somehow; from the banked source it cannot have been. Whatever produced those canonicals is unverifiable against the archived source by any mechanical means. Not part of this item; named because it was found and would otherwise be lost.
• Boundary cases needing eyeball before any of them gate a graduation: function-of-dynamics-haydn-mozart-beethoven reads 4,537 words/page on 1 font — implausible for a book page and probably an extraction artefact; the-arcades-project-walter-benjamin-pdf reads born-digital on 1,664 fonts, a font count far more characteristic of OCR, and may be a scan whose images fall under the classifier's page-image threshold. The classifier is sound enough to establish that the tier split is needed; it is NOT yet sound enough for its per-file verdicts to gate anything. Per §VII, eyeball-after-gate is discipline where no stronger mechanical check exists — these are exactly that case.

Negative control: satisfied, abundantly. The earlier concern that a classifier which has only ever returned born-digital has not been shown able to return scanned is discharged: across 385 library PDFs it returns 164 bare-scan · 59 scanned-with-OCR · 62 born-digital, and within the canon 44 scans against 16 born-digital. The instrument demonstrably detects both presence and absence.

Unchanged: the V-DPDF recommendation of Addendum 1, and the hold on Harrison's graduation stamp. Awaiting: Steward authorization on the V-DPDF shape, reading the exposure figures from THIS addendum and not from the original item.

PENDING-83 — ADDENDUM 3 (2026-07-28): routed to the jurist; the framing is corrected a third time

Jurist package filed: ~/_Dev/chamber-library/docs/vdpdf-tier-JURIST-PACKAGE-2026-07-28.md (self-contained; 45 quoted clauses verified verbatim against the ratified spec with a positive control; five gate questions with executor leans).

Third correction, and it inverts the item's premise. The original item and both prior addenda argued that tier_of() was wrong — that the code decided the tier by file extension where the constitution intended otherwise. Reading §Tiering & Fence from the substrate (rather than from the repo CLAUDE.md summary I had been quoting) shows the opposite: the ratified evidence-tier table itself enumerates the tiers by format — "V-TEXT (born-digital: epub/azw3/mobi)" and "V-SCAN (scanned pdf)". The suffix map in the code reproduces those parentheticals exactly. The code is faithful; the constitution is what conflates the container with the origin. A reviewer comparing code against spec would find agreement, which is why the defect survived — and it is why this is a constitutional supersession rather than a code fix.

The argument is also stronger than filed. The same ratified subsection carries the anti-bypass clause: "a text-bearing work is verified by the method declared for text-bearing kinds, and no work may weaken its applicable method by declaring itself a new kind." A born-digital PDF is text-bearing, and §V confirms "Tier 3 governs every canonical whose content is words." The weakening that clause forbids is therefore already occurring — not because any work declared anything, but because the table's format enumeration performs the re-labelling automatically by reading a file extension. Whether that reading extends the clause past its ratified reach is put to the jurist as Q4 rather than assumed.

A fabricated quote was caught in the package's own Grounding section before filing. The draft rendered a promotion-criterion clause as "the §V prose-word guard we already have." The spec says "the §V prose-word guard we already run is the promotion test. The bar for 93% (1,191/1,284) of the corpus." — invented ending, in the one section whose entire purpose is that the jurist can trust the wording without repository access, in a package about verification. Caught by a mechanical containment check over every quoted line, run with a positive control; the true text is materially stronger for the argument than the invention. Recorded rather than quietly repaired: it is the fourth instance today of a claim composed from a summary of a document rather than the document.

Awaiting: jurist design-gate ruling (steward-relayed), then steward authorization. Harrison holds at the graduation stamp; its prior steps are unblocked and unaffected.

PENDING-83 — ADDENDUM 4 (2026-07-28): design gate PASSED with two required corrections

Ruling filed verbatim: ~/_Dev/chamber-library/docs/vdpdf-tier-JURIST-RULING-2026-07-28.md. Executor disposition: the Addendum appended to docs/vdpdf-tier-JURIST-PACKAGE-2026-07-28.md (Parts I–VIII preserved unrewritten as the text ruled on). REVIEWED-83 drafted for steward placement — in the ruling and the package Addendum, plain-fenced.

Q1, Q4, Q5 affirmed as filed; Q4 on stronger grounds than argued (REVIEWED-75's drafting note states the anti-bypass guard was rebound "to the property, not enrollment" because the declaration-only reading "would open the moment the door is first used" — the extension is inside the clause's ratified reach). Two corrections supersede the drafted design: (1) independence of the reference conversion from the ground-truth extraction is a constitutional requirement, not declared data — and REVIEWED-72's V-TEXT precedent must not be carried across, because it ruled the other way (a shared pandoc reader was accepted there since reader-loss cancels a priori over unambiguous markup; PDF recovery is inference over page geometry, so nothing cancels). (2) the demonstration is of two instruments, and the executor conflated them: the classifier's controls are complete, but the verification method has no control at all, and requires a deliberately constructed column-order corruption case run through a genuinely independent extractor pair. Harrison's graduation stamp holds until that passes; its earlier steps proceed. Awaiting: steward placement of REVIEWED-83, then the Q3 demonstration.

PENDING-84 — Nine canonicals whose banked sources carry no extractable text at all (TRIAGED + CLOSED 2026-08-01 — the defect is dispositioned, not repaired; see the census)

Date: 2026-07-28 Tag: [HARDENING] Summary: Nine canonicals resolve to archived sources with zero embedded fonts and zero extractable words (bare scans), yet their canonical texts exist — so the text came from somewhere that is not mechanically recoverable from the source of record. Rationale: Surfaced by the PENDING-83 census and docketed separately on the jurist's process note (PENDING-55 residual-item precedent: findings named-not-lost still have to be findable). Whatever produced these canonicals cannot be re-derived from the banked source by any extraction, which means they are unverifiable against their own provenance by any tier's method — not V-SCAN's, not a future V-DPDF's. This is a distinct condition from "hard to verify": it is "no mechanical path from the source of record to the canonical exists." Instances observed 2026-07-28 include mal-darchive and on-textual-understanding-szondi; the full set of 9 is in the census. Recommendation: Read one end-to-end first — establish what actually produced the text (a prior OCR run whose output was not banked? a different edition?) before proposing a class remedy. Diagnose the class, but from one real instance rather than from the count. Files affected: none yet — diagnosis precedes any change. Awaiting: Steward triage of priority. Not urgent; not to be lost.

PENDING-84 — DIAGNOSIS (2026-08-01), from one instance read end-to-end, then bounded across the class

The nine are six works, and the count concealed that. Reproduced by re-running the classifier over Chamber Sources: 9 bare-scan sources, of which four are one work — Alexander's Nature of Order vols 1–4. The rest: detail-in-typography-hochuli, mal-darchive, on-textual-understanding-szondi, pedagogical-sketchbook-klee, typography-ruder. Diagnosing "nine canonicals" invited a class remedy for what is six conversions, four of them one batch.

The instance read end-to-end: mal-darchive. What produced the text is already recorded in our own runbook — it did not need investigating, it needed reading. _curation/conversion-runbook.yaml known_gaps.research, dated 2026-07-12: "Docling+OCR CROSSES this frontier — it OCR'd a scanned French book (mal-darchive) with 104 footnotes + full page-provenance, 0 cruft, on the M4 (~11min)." So the canonical came from an OCR inference run during the PENDING-56 four-tier trial, whose output was never banked as a derived artifact. That is why no extraction reproduces it: the source is a bare scan, extraction yields nothing, and the text exists only as the output of a model run that was not retained. The canonical still carries the run's signature — 137 <!-- page N --> markers, matching the "full page-provenance" claim.

And the same runbook entry names the damage, in the same breath: "output is readable but NOT verbatim-clean (glued words, I→1, dropped accents)". Measured against the corpus rather than assumed: French canonicals carry 255.8 accented letters per 10,000 characters (median, n=34; top of range 263–309 — Proust 275.8, Camus 268.1, Foucault 287.5). mal-darchive carries 0.4. Zero overlap, a ~600× gap. Its diacritics are not reduced, they are gone — Conference prononcee le 5 juin 1994 a Londres, Galilee, Ne commencons pas, Deja, soupconnons. Under §V that is Tier-3 alteration by omission on nearly every line of a French text, and it is the same shape REVIEWED-70 ruled on for character-bearing images: "a lexical change no less than a substitution would be." The work is in canon in that state.

The class-level finding, and it is not the one the item names. All nine were checked for the §V mandatory conversion record: 9 of 9 have none. Seven have no frontmatter at all (mal-darchive, detail-in-typography-hochuli, all four Alexander volumes, pedagogical-sketchbook-klee); the two that do (on-textual-understanding-szondi, typography-ruder) carry no conversion field either. §V: "Every conversion — OCR or EPUB, first-run or re-extraction — must produce a conversion record." §VII: "A canonical text without a conversion record is not verifiable and cannot enter canon." Nine canonicals are in canon in violation of that clause. The missing record is the actual defect: it is why the producing run is unknown, and it is a condition the corpus can repair without re-running any OCR.

The class is also wider than bare scans — the condition is "no mechanical path," not "no extractable text." Found while closing PENDING-85: ulysses-james-joyce resolves to Ulysses (Cliffs Notes) (James Joyce).pdf, matched match_cov: 1.0, match_conf: high on title-plus-author. Its canonical is the real Penguin Ulysses (288,602 words, conversion_method: calibre, source unbanked). A wrong work banked with abundant extractable text produces exactly the same condition as a bare scan. Any census scoped to verdict == bare-scan will keep missing this member, and the source-matcher's own step-4 warning already predicted the failure mode: "A high title-match is NOT proof."

What this diagnosis does NOT establish, stated so it is not read as settled: the producing run is documented for mal-darchive and inferred-by-family for the four Alexander volumes (the runbook names Alexander as the ocrmac multi-column case and records "the page-number method (Alexander 9/9)"); Hochuli, Szondi, Klee and Ruder were not traced — that is four works still genuinely unknown, and I did not read them end-to-end. Diacritic loss was measured for the French instance only; the English-language members give no diagnostic signal from that measure and need a different probe. No remedy is proposed here, and nothing was changed.

Falsifiers, one command each: grep -n "mal-darchive" _curation/conversion-runbook.yaml returns the 2026-07-12 entry with the dropped-accents caveat; head -1 on any of the seven shows no ---; the accented-letter rate is a four-line script over canonical_texts/**/*.md. If any of the nine turns out to carry a conversion record, the class finding fails. Awaiting (unchanged in kind, sharper in content): steward triage. The cheapest closable piece is the conversion-record gap (a records defect, no OCR re-run); the expensive piece is mal-darchive's diacritic restoration, which requires re-conversion, not repair.

PENDING-84 — TRIAGE + CLOSURE (2026-08-01, steward-directed)

The item's own question — "steward triage of priority" — is answered, so the item closes. The corpus defect does not: it is dispositioned and relocated to a durable artifact, not repaired. Saying otherwise would be the false-closure shape this corpus exists to prevent.

What was built: the §VII quarantine artifact — _curation/provenance-gap-2026-08-01.tsv. Nine rows: canonical slug · path · live sha256 · frontmatter present · source file · source sha256 · condition · converter · converter_basis · evidence. Zero canonical bytes changed — no hash churn, no re-anchor, and the binding surface was checked first: all nine are catalogue-bound but unbound in the engine (no corpus/manifest.yaml entry, no sidecar, no reading-index), so the blast radius is chamber-only and this artifact does not even touch it.

Why a separate file and not frontmatter — the constitution rules it, and the ruled case has now arrived. §VII: "a datum provable only by production, never by an independent gate, goes to a quarantine namespace trusted consumers structurally cannot read (a separate sidecar or _unverified.*), never a first-class field under a soft gate — this quarantine lane is the designed answer for a case that has not yet arisen; designed, not built." These nine are precisely that case: their provenance is provable only by the production run, never by an independent gate. Writing it into canonical frontmatter would place production-only provenance in the trusted namespace, where presence would read as compliance — PASS-BUT-FALSELY, in the exact field whose absence is the defect. The lane was designed for a hypothetical; the hypothetical is here.

converter_basis is the load-bearing column, and it is three-valued on purpose (attest-never-default): attested = a durable record names the run — 1 of 9, mal-darchive, on the runbook's own 2026-07-12 entry; inferred = family-level evidence only, explicitly not a conversion record — 4 of 9, the Alexander volumes, on the runbook naming Alexander as the multi-column ocrmac case and recording "the page-number method (Alexander 9/9)"; unknown = no evidence found and none guessed — 4 of 9: Hochuli, Szondi, Klee, Ruder.

What this explicitly does NOT do: it does not satisfy §V, does not make any of these texts verifiable, and does not lift the §VII bar on canon entry. The violation stands. What changed is that it is now legible rather than silent — which is the whole of what a records act can honestly buy.

The remedy, scheduled rather than deferred (a named order, not a vague later):

1. mal-darchive — first, and it is the only one with demonstrated text damage. Diacritics measured at 0.4 per 10k against a French-corpus median of 255.8 (n=34): Tier-3 alteration by omission on nearly every line. Requires re-conversion, not repair; the source is a bare scan, so this is an OCR run (M4), and the runbook's own caveat predicts the failure mode to guard against.
2. The four Alexander volumes — one batch, one campaign. No demonstrated text damage; the defect is the missing record. They are a single work in four volumes and should be re-converted together or not at all.
3. Hochuli, Ruder, Klee — schedule against chamber-typography, which is the workstream that actually reads them. Szondi against whichever workstream calls for it. Nothing here is urgent by exposure: none of the nine is engine-registered, so none is currently serving the engine as verified text.

Falsifier: if any of the nine turns out to carry a conversion record, or to be engine-bound, the census row is wrong and the disposition needs revisiting. Both are one grep.

PENDING-85 — Two PDF-origin classifier verdicts require human eyeball before any per-file use (CLOSED 2026-08-01)

Date: 2026-07-28 Tag: [FIX] Summary: Two of the 60 classified canonical PDF sources carry verdicts the classifier's own numbers make doubtful, and they must be eyeballed before any per-file verdict is relied on. Rationale: the-arcades-project-walter-benjamin-pdf classifies born-digital on 1,664 embedded fonts — a count far more characteristic of OCR output than of typesetting, suggesting a scan whose page images fall below the classifier's page-image threshold. function-of-dynamics-haydn-mozart-beethoven reads 4,537 words/page on 1 font, implausible for a book page and probably an extraction artefact. Both were stated as caveats on the instrument's own output (§VII: a measurement carrying a known reliability caveat states it in the same breath as its count) and the jurist affirmed they were correctly held out of the PENDING-83 population claim. The population claim (16/44) does not depend on either. Recommendation: Open both PDFs and look. This is §VII's eyeball-after-gate, which the spec names as the genuine ceiling where no stronger mechanical check exists — not a deferral. Files affected: none — a reading task; may yield a threshold correction to the scratchpad classifier. Awaiting: Nothing blocking; do before the classifier's per-file verdicts gate anything.

PENDING-85 — DISPOSITION (2026-08-01): both eyeballed. One verdict WRONG, one CORRECT with the doubt misdiagnosed — and the class is larger than two.

Executed as §VII eyeball-after-gate: pages rendered with pdftoppm and read, not inferred from metadata. The classifier (classify_pdf_origin.py) was re-run first with --selftest PASS 8/8 including its live Harrison control, and both verdicts reproduced exactly (502.9 w/pp · 1,664 fonts; 4,537 w/pp · 1 font).

1. the-arcades-project-walter-benjamin-pdf — verdict WRONG. It is scanned-with-OCR, not born-digital. Producer: Adobe Acrobat 9.2 Paper Capture Plug-in with ClearScan — Paper Capture is Acrobat's scan-OCR module, and ClearScan replaces the scanned bitmap with fonts synthesised per glyph-shape. 923 of the 1,664 fonts match Fd<hex>-Identity-H CID Type 0C (a deliberately conservative pattern — the true synthetic count is higher; stated as an under-count per §VII). Rendered p.440 settles it visually: baseline wobble, uneven inter-word spacing, blob artefacts (ba■ly, a stray mark after 1804,), a spurious mid-word dot in Gour·don, broken glyphs in communication, and a running head whose ornament is recognised as M. The canonical carries matching damage — converted_with: pdftotext, and fragmented OCR-line headings (## Prepared On The / ## The Basis / ## Basis Of The / ## The German Volume / ## Volume Edited). 512,549 words. This work belongs to the scan tier, where eyeball-after-gate already governs.

2. function-of-dynamics-haydn-mozart-beethoven — verdict CORRECT; the stated doubt is refuted; a worse defect is underneath it. Pages: 1, page size 1083 × 6882 pt — one sheet ≈ 9.6 letter pages, Producer: macOS … Quartz PDFContext. So 4,537 words/page is arithmetic on a page count of one (≈470 words per notional page) and is not an extraction artefact. It is genuinely born-digital. But the rendered page shows what it actually is: a browser print-to-PDF of the College Music Symposium web page — nav bar, JOIN TO COMMENT, search box, hashtag list, a JSTOR link, comment form and site footer. pdfinfo/pdffonts both emit Internal Error: xref num 151 not found but needed, try to reconstruct — the source is structurally damaged. And the canonical has no frontmatter at all (first line is <!-- image -->), carries the site chrome verbatim, and duplicates title and byline where the print rendering doubled them. 204 lines, 4,558 words.

3. The class-level defect — and PENDING-85's own hypothesis is refuted. This item guessed a threshold problem (a scan whose page images fall below MIN_PAGE_IMAGE_PX = 800). Measured: wrong. ClearScan discards the page bitmap, so there is no page image at any size — the triad's third leg is structurally absent for the whole family, and no threshold reaches it. Worse, a second instance exists that the structural test also cannot see: tschichold-form-book (Creator: ABBYY FineReader, 0% synthetic-CID) is OCR'd and re-typeset into real embedded fonts, so its rendered pages look perfectly clean. Its OCR signature survives only in the words — p.82 reads Matthias Griinewald (ü→ii) a few lines after a correctly-set Grünewald in the same paragraph. For the OCR-then-re-typeset family, structure is insufficient and the cheap discriminator is the metadata the classifier's docstring deliberately distrusts — the inverse of its stated design premise. Any remedy must add a fourth signal (producer/creator strings plus an OCR-error probe over the extracted text), not adjust a threshold.

4. Census — the born-digital set is fully examined, and the population figure is wrong. All 16 Chamber-Sources PDFs the classifier calls born-digital were checked: 12 carry unambiguous typesetting-software Creator (InDesign, QuarkXPress, XSL Formatter, Acrobat PDFMaker, Word); mla-9th-ed, ulysses-james-joyce and aldus-manutius-margolis had absent or ambiguous metadata and were eyeballed — all three confirmed born-digital. Two are OCR'd (items 1 and 3). So: genuinely born-digital sources of record = 14. Two separate corrections follow, and the second touches ratified text:

• Re-running the same classifier over the same folder gives 16, not the 17 stated on 2026-07-29. That package already flagged a 17-vs-16 discrepancy against a different census and left it unchased; it is now a second unreconciled count of the same population — the instrument-defines-its-own-count class again.
• 0 of 17 is quoted in ratified spec v2.9.0 and in chamber-library/CLAUDE.md. The zero is unaffected — removing members from a population cannot create a two-column instance, so the ruling's argument strengthens. Only the denominator is wrong, and the honest figure is 0 of 14. Correcting ratified text is not the executor's to do; surfaced here, not edited.

5. A defect in the classifier's own metadata reader, found by its own output. re.match(r"^Producer:\s+(.*)$", info, re.M) — \s matches a newline, so an empty field silently reports the next field's value. Observed live: tschichold-form-book reported Producer: CreationDate: Wed May 5 23:14:25 2010 CEST. A reader that fabricates a value from an adjacent line is the false-datum class §VII names; the corrected read (^([A-Za-z ]+):[ \t]*(.*)$) is what produced item 3.

6. Adjacent finding — a PENDING-84-class instance that is not a bare scan. ulysses-james-joyce resolves to Ulysses (Cliffs Notes) (James Joyce).pdf — a study guide, matched at match_cov: 1.0, match_conf: high because title and author both appear. Its canonical is the real Penguin Ulysses (288,602 words, conversion_method: calibre, from a different and unbanked source). Its text therefore cannot be derived from its source of record either — which widens PENDING-84's class: the condition is "no mechanical path from the source of record to the canonical," and a wrong work banked with plenty of extractable text produces it exactly as a bare scan does. PENDING-84 should be diagnosed against that wider class, not against nine bare scans.

What would falsify this disposition: open Chamber Sources/the-arcades-project-walter-benjamin-pdf.pdf at p.440 and tschichold-form-book.pdf at p.82 — if the letterforms are uniform and Griinewald is not there, items 1 and 3 fail. pdfinfo on either reproduces the producer strings in one command; pdfinfo function-of-dynamics-…pdf | grep -E 'Pages|Page size' reproduces item 2 in one.

Not done, deliberately: no classifier code was changed (it is scratchpad-only and wired to nothing, and the remedy is a new signal, which is instrument work the steward has deprioritised behind the corpus); no ratified text was corrected; no re-tiering of Arcades or Tschichold was applied. ⚠ The classifier lives in an ephemeral session scratchpad (/private/tmp/claude-501/<session-id>/scratchpad/classify_pdf_origin.py) — it is the evidence instrument behind PENDING-83/REVIEWED-83 and will be lost on cleanup.

SUPERSEDED, same day — the two paragraphs above no longer hold. On steward authorization (2026-08-01, bounded scope, explicitly "no rabbit hole") the classifier was repaired and promoted to the fleet: scripts/classify_pdf_origin.py, commit 08ae83e, on both remotes. Fourth signal added (declared OCR-producer registry), meta() newline defect fixed, --validate 20/20 including live Harrison and Arcades regression pins, test_tools.py coverage, fleet 300/300. Bounded-change proof over all 63 Chamber-Sources PDFs: exactly 2 verdicts moved, 61 unchanged; new distribution scanned-with-OCR 40 · born-digital 14 · bare-scan 9. Residual blindness declared on every run per §VII (UNATTESTED-BY-METADATA; one file in that state today, mla-9th-ed, eyeballed clean). Still not done, and still deliberately: no ratified text corrected (routed via REVIEWED-83 Amendment 1, drafted, awaiting placement), no canonical re-tiered, no gate touched, and no OCR-error text probe built — that reaches the metadata-stripped family but is a per-language research problem, and the registry closes both instances that exist.

PENDING-86 — The jurist cannot read the constitution it design-gates

Date: 2026-07-28 Tag: [HARDENING] Summary: governance_read exposes claude-md, pending, pending-archive, reviewed, app-brief and memory-index — but not chamber-library-specification.md, so a constitutional supersession of §Tiering & Fence was ruled on by a party who could not read §Tiering & Fence. Rationale: Disclosed by the jurist unprompted at the head of the PENDING-83 ruling, which is the mechanism working: it corroborated the package's load-bearing quotes against REVIEWED-75/-72/-67 and PENDING-55 — genuinely independent of the package, but one layer short of the primary substrate, and said so rather than letting the ruling imply a check it had not made. The ruling's substance is unaffected; the standing arrangement is the problem. This is the same shape as the defect PENDING-83 repairs, one level up: an instrument reporting on a domain it does not reach. At present the only instrument reading the primary substrate for this class of package is the executor's own verbatim self-check — which is exactly what should not be sole, since that self-check caught a fabricated quote the executor had itself introduced into the Grounding section of a package about verification. Options: (a) add the chamber constitution (and graduation-spec.yaml) to governance_read's document keys, read-only, alongside the existing six; (b) keep the jurist repo-blind by design and require every package to carry a mechanical verbatim-containment proof over its quoted clauses, reported in the package; (c) both; (d) [ADDED 2026-07-29, per the PENDING-87 ruling's process note] a keyword search across PENDING.md/PENDING-archive.md/REVIEWED.md, not only keyed retrieval of documents whose IDs are already known. Recommendation: (c) plus (d). (a) removes the gap for the documents the loop actually rules on and costs two keys on an already-built read-only server; (b) is worth keeping regardless, because self-containment is what makes a package rulable at all and the containment check has already proven it catches executor fabrication. They are complements, not alternatives. Files affected: ~/dotfiles/scripts/governance-mcp.py (document keys; a search entry point for (d)). Extends PENDING-82. 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. (d) ALSO AUTHORIZED + LANDED 2026-08-05 (6738239). governance_search(query, limit) over the three governance files; result unit is the item, boundaries from wd.item_spans (no second parser), results naming ids to hand to governance_item so the two tools compose. Terms are ANDed and that is disclosed on every result, and a miss is a legible empty stating corpus, items scanned, terms and match mode — the engine's PENDING-97 failure shape is not being rebuilt here unannounced, and PENDING-96's disclose-your-blindness discipline is applied to a new instrument on the day it was ruled. Ranked by exact-phrase then raw term-count, labelled a count, not a relevance score.

The structural pass earned itself immediately, and this is the substantive finding. Search carries a query-independent check for item headers hidden by leading whitespace — invisible to item_spans, therefore unable to appear in any result, so their absence reads as a genuine miss. It found three: REVIEWED-11, REVIEWED-12 and REVIEWED-74. The last is precisely the ruling the 2026-07-29 amendment says the jurist could not find — so that failure was over-determined: it did not know the id, and governance_item('REVIEWED-74') returned NOT FOUND. The executor may not edit REVIEWED.md (Constitutional Constraint 1), so the census was handed to the steward, who unindented all three in-session. Items visible 78 → 81; hidden headers now zero, with a negative control that goes red if one is ever hidden again. Selftest 29 → 44 controls, 0 fail.

⚠ Both (a) and (d) require a Claude.app restart — the running server carries the old code.

(b) stands built and in use (check_containment.py, applied to the PENDING-99 package: 16/16 contained, 9/9 controls absent). This item is now fully dispositioned: (a) landed · (b) standing · (c) = (a)+(b), satisfied · (d) landed. Ready to close on steward confirmation.

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

Date: 2026-07-29 Tag: [PROPOSAL] Summary: REVIEWED-83 Q3 requires a constructed column-order corruption "run through the actual candidate reference-converter pair, confirming the guard flags it" — but the guard is coverage-based and provably order-blind at block scale, so no extractor pair, however independent, can make it flag; the precondition should be reformulated as the position-sensitive comparison the Eichmann pilot §7 already names. Rationale: Two facts settle it, both measured 2026-07-29 and both quoted from the substrate in the package. (1) Independence exists — four PDF extractors with zero shared libraries by otool; docling recovers correct column order on an adversarial hand-authored two-column fixture (similarity 1.000) where poppler, MuPDF, PDFium and pdfminer all return content-stream order (0.550), byte-identical to poppler's documented -raw. So Q2's held-if-no-independent-pair fallback does not fire. (2) The operator, not the pair, is the blocker — running the repo's own verify_body_conservation.classify on a real canonical, a fully block-reversed text scores 100.00% match, 0 added, 0 interior lost, PASS against a correct reference, while a token-level shuffle FLAGs at 0.00%. Coverage sees token-level disorder and is blind to block-level moves. This was already demonstrated on a real book (Eichmann pilot §7, 2026-07-19) and already dispositioned by the jurist 2026-07-24 as the standing Q3 order-blindness block gating the verified stamp rather than the door — neither document was supplied to the jurist on 2026-07-28, which is an executor self-containment failure, not a defect in the ruling. The measurement the reformulation needs is now in hand: order-concordance over shared k-grams separates clean from corrupted at 0.995–1.000 vs 0.117–0.411 (gap 0.583, zero overlap) across 33 book×extractor pairs, with content-overlap (0.551–0.982) orthogonal to it. A column probe over all 84 born-digital PDFs found exactly one predominantly two-column book, and it scores 0.995–0.999 clean — no false positive on the corpus's only real instance of the hazard. Options: (a) reformulate Q3 as the §7 position-sensitive extension, with the measurement above as its feasibility evidence; (b) take blocking condition (a)'s other ratified branch — "an explicit, argued acceptance of eyeball-after-gate as the genuine ceiling"; (c) waive Q3 and ratify V-DPDF without an order condition. Recommendation: (a), with (b) live. (c) is refused: it would leave the stamp attesting an order it never measured, which is the false-ABSTAIN shape PENDING-55 named — a false ABSTAIN is as much a lie as a false PASS. The evidence is strong enough to argue the mechanical route is feasible and weak enough that it does not yet earn ratification: the corruption is simulated by block-reversing docling's own output, the sample is 11 books at 40 interior pages rather than a census, and the executor's own synthetic-fixture prediction that real two-column books would false-flag was refuted by measurement and is corrected in the package. Files affected: none mutated. Package drafted at chamber-library/docs/order-attestation-JURIST-PACKAGE-2026-07-29.md (30/30 quoted passages verified by mechanical containment, positive and negative controls passing). All instruments scratchpad-only, wired to nothing. If ratified: a MINOR supersession of §Tiering & Fence + graduation-spec.yaml order_attestation: as declared data. Awaiting: Jurist design gate, then steward authorization.

PENDING-88 — The skill-harvest loop has no FIX lane, and its surface has outgrown its own readability

Date: 2026-07-29 Tag: [PROPOSAL] Summary: /wrap-up §1.6 requires that skill changes be proposed only — "never create, patch, or retire a skill autonomously at wrap" — with no change-class distinction, so a template gaining a section and a change to an authorization boundary are governed identically; the resulting queue is 151 PROPOSED against 26 BUILT + 13 AUTHORIZED, oldest open batch 2026-06-05, in a register now 166 KB — over the read cap, which means the /wake-up step that exists to surface open proposals cannot read them. Rationale: This is not the contamination mitigation working as designed; it is a flattening of the ratified taxonomy. ~/CLAUDE.md already rules the question directly: "Claude Code improving its own diagnostic capability is not self-modification — it is the system doing what it was built to do. The steward remains in the loop through [PROPOSAL] and [ESCALATE] tags." The taxonomy it names has a FIX lane — "[FIX] Resolves a scoped bug against existing specification · Requires: Nothing — implement directly" — and §1.6 does not use it. The cost is now measurable and compounding: proposals are not rejected, they are filed into a file neither party can read, and the mechanism meant to bring them to the steward has failed silently since the 2026-07-22 tripwire. The steward's own statement of intent (2026-07-29): "I never meant to forbid that as long as I was made aware of what needed to be improved and why. In fact, I need you to be able to do so — I cannot think of everything." Note also the shape of what is stuck: today's four proposals (a ## What held ledger section, a prevention KG predicate, one line at the wake, a reframed standing question) change what gets recorded, not what the executor may do — the class most starved by a blanket gate, and the class whose absence produced the "ledger of failure" the steward named tonight. Options: (a) status quo — everything stays PROPOSAL; (b) a change-class test for tooling, mirroring the chamber's ratified one ("does this change what any gate accepts?"): does this change what the executor may do without asking, or what a governed artifact asserts? NO → FIX: apply it, and report it in the wrap with what changed and why, plus a provenance comment in the skill source. YES → PROPOSAL, unchanged; (c) (b) plus a standing hard floor that remains PROPOSAL/ESCALATE regardless of class; (d) compact the register (owed since 2026-07-22) with no rule change. Recommendation: (c), and (d) regardless of the rule decision — the unreadable register is a mechanical defect breaking the loop today, independent of who may change what. The hard floor must be explicit and is the part the steward should scrutinise hardest: anything touching ~/CLAUDE.md / ~/REVIEWED.md / L2 constitutional documents (Constraint #1); anything altering an authorization boundary, a gate's acceptance, or the loop itself; anything touching logchain append / cursor persistence / module registration (Constraint #2); and — the one most relevant to this item — anything that would reduce what gets surfaced to the steward, since pre-filtering for comfort is the named contamination failure and a self-granted FIX lane is exactly where it would appear. Files affected: ~/.claude/skills/wrap-up/SKILL.md §1.6; ~/.claude/skills/wake-up/SKILL.md §2.a (the register read that currently cannot complete); skill-harvest-register.md (compaction). Executor's declared interest — and a correction to how it was first stated (amended 2026-07-29, steward-challenged). This item would loosen a constraint on the executor, proposed by the executor, immediately after the steward invited it. The interest is real and is stated so it cannot be read without seeing it. But the first draft of this paragraph over-claimed, and the over-claim was itself the failure it warned about. It implied the proposal should be discounted because the steward would welcome it — which makes welcomeness the evidence, and would disqualify every correct thing the executor ever produces. The steward's challenge: "Does 'pleases you' and 'successfully achieve what's necessary' mean two different things? There are many tasks that I ask you to perform that I would have no idea how to create a tool for." Both halves land. (i) The two coincide whenever the true answer is also the welcome one; contamination is the case where they diverge and the output bends toward comfort. (ii) For an instrument the steward could not have specified, deference has nothing to defer to — there is no interlocutor-position to drift toward, so the pressure has no target and what remains is only whether the tool is right. (iii) Performing scrupulousness is itself pleasing — cheap, safe-looking, and it buys the executor the appearance of rigor at the cost of a working tool. ~/CLAUDE.md: "Deference that lets the human waste time is not respect — it is a failure of the partnership." The discipline that actually applies is answerability, not purity — the chamber's own thesis, turned on the executor: "you don't make the reader trustworthy by purifying it. You make it answerable by binding it to the marks" (the Chamber touchstone, §2). So the operative mitigation is not the disclosure; it is that every load-bearing claim here is one command from refutation: 151 PROPOSED / 26 BUILT / 13 AUTHORIZED and 166 KB from skill-harvest-register.md, oldest open batch 2026-06-05, the §1.6 blanket rule and the [FIX] taxonomy row quotable verbatim. What would falsify the item: if the register reads under the cap, or if the PROPOSED backlog is small or recent, the diagnosis fails and option (a) stands. Remaining structural mitigations, unchanged: the recommendation adds a hard floor rather than only removing a gate; the FIX lane carries a mandatory report, preserving awareness by disclosure rather than permission; and this is filed as [PROPOSAL], not implemented — which its own proposed test also requires, since changing what the executor may do is exactly the PROPOSAL-class case. Awaiting: Steward authorization.

PENDING-88 — AMENDMENT (2026-08-01): option (d) is already authorized, and its authorized METHOD cannot work

Measured against the register itself before acting. Four corrections; the item's direction survives all of them, its numbers and its remedy do not.

1. (d) does not need a ruling — it has one, from 2026-07-19. The register's own head block is authoritative: "Stroke 4 — register compaction: AUTHORIZED; same slot as Stroke 2". The compaction has been authorized for six weeks and simply never executed. Stroke 2 — the verification-ladder batch-append, "ALL earned ladder entries queued in this register (~25–30)" — is authorized and unexecuted in the same slot. Two authorized housekeeping acts, both waiting on a slot rather than on the steward.

2. The authorized method is inapplicable to the actual condition. Stroke 4 prescribes "ruled items collapse to verdict lines; detail stays in git history." Measured over the file: of 190 table rows, 13 are ruled (8 BUILT · 4 AUTHORIZED · 1 DEFERRED) and 177 are open. Collapsing every ruled row would remove ~7% of the register. It is not large with settled history; it is large with open proposals. The prescribed remedy leaves it over the cap and the loop still broken.

3. The counts in this item are unreliable — and so were mine until I stated a rule. The item claims 151 PROPOSED against 26 BUILT + 13 AUTHORIZED. Counting markdown table rows with ≥5 pipes, excluding header and separator rows — stated so it can be checked — gives 123 PROPOSED · 54 unmarked · 8 BUILT · 4 AUTHORIZED · 1 DEFERRED. The BUILT/AUTHORIZED gap is because most ruled history lives in the "Built / authorized (lineage)" bullet list and in prose blocks, which no table-row counter sees. Fourth instrument-defines-its-own-count disagreement today. The item's own falsifier is NOT triggered: the file is 166,589 bytes (over cap; the item's "166 KB" is exact), 177 open is not small, and the oldest open item is 2026-05-24, not recent. The diagnosis stands; the arithmetic should be restated with a rule.

4. A structural defect the item does not name, and it is most of the file. One section — ## New proposals (2026-06-13 post-clear — …) — spans 411 lines / 96,848 bytes = 58% of the register and contains 33 distinct dates running 2026-05-24 → 2026-07-19. Five weeks of wrap-appends landed in an existing section instead of new dated ones, so the register misreports its own chronology: "oldest open batch 2026-06-05" undersells it by twelve days, and §1.6's append step is silently mis-filing.

A method that does work, with a house precedent that already succeeded: the MEMORY.md two-file split (2026-07-06 — 213 KB → 17 KB, 91.8%; live index + reference layer). Applied here: a live index of open proposals (one line each: skill · kind · one-line · date · status), full rationale/origin prose relocated to skill-harvest-archive.md. Sizing: 177 entries × ~110 bytes ≈ 19 KB — cap-clearing, and lossless in the working tree, so nothing depends on git recovery. It compacts by form, not by dropping items — required here, because dropping open proposals would cross this item's own proposed hard floor ("anything that would reduce what gets surfaced to the steward"). Git-backing verified regardless: the memory directory sits inside ~/dotfiles and the register is tracked.

Why proposed and not applied. Stroke 4's authorization covers compaction; it does not cover this method, and the change is not cosmetic — it restructures the surface that decides what reaches the steward. By this item's own test, that is PROPOSAL-class.

It sharpens the recommendation rather than replacing it. 177 proposals opened since 2026-05-24 against one full review (2026-07-19) is the actual cost driver. Compaction is hygiene on the symptom; the FIX lane in (b)/(c) is the load-bearing half — without it the register re-bloats, exactly as MEMORY.md re-bloated after the 2026-06-08 compress-in-place pass "attacked the level not the class." Recommendation unchanged in substance, corrected in method: (c), plus (d) executed by split rather than by collapse.

PENDING-89 — The Q3 correlation review: are jurist and executor misses clustered?

Date: 2026-08-02 Tag: [HARDENING] Summary: Run the falsifier the differently-biased-checkers doctrine names against the existing PENDING/REVIEWED record, rather than leaving it hypothetical. Rationale: REVIEWED-86 left Q3 — do two Claude instances constitute a check, or only a second reading? — explicitly unresolved, and the doctrine text placed at Constraint 6 says in its own words that neither it nor its supporting evidence establishes the jurist–executor pair as a check in the strong sense. The package named the test that would settle it: whether jurist and executor errors cluster in the same classes while steward corrections catch a systematically different class. The jurist's ruling notes it is checkable now, on the rulings that exist, and should be docketed rather than float. If misses cluster, the doctrine is false for this configuration and must be weakened to "only the steward supplies genuine independence; jurist review is a second reading, valuable and not a check." Options: (a) run it on the four most recent rulings only (REVIEWED-83 to -86) — fast, but n=4 and all from one arc; (b) run it across the full REVIEWED/PENDING record — larger n, but the older entries predate the current three-party discipline and may not be comparable; (c) run (a) now as a pilot with its own pre-registration, and use it to decide whether (b) is worth the cost. Recommendation: (c). The same shape as the Fool trials and the 2025 archive read: pre-register what counts as a clustered miss before reading, or the executor grades its own errors after seeing them. Note the standing hazard — this is the executor measuring whether the executor is checked, which is the contaminated form; the grading criteria must be fixed in advance and the raw classifications left checkable. Files affected: none yet; a measurement, not a change. Output would be a dated record beside the doctrine package. Awaiting: Steward direction on (a)/(b)/(c), and on whether the executor is the right party to run a measurement of its own oversight at all — the jurist is no more independent here, so this may be steward-only work.

PENDING-90 — First L2 transfer: checker position in the calibration loop

Date: 2026-08-02 Tag: [ESCALATE] Summary: A candidate amendment carrying the differently-biased-checkers doctrine (Constraint 6) into the CapableMind spec corpus is drafted and awaiting steward authorization; it proposes an autonomy-ceiling rule, which is L2-constitutional. Rationale: Five months of microcosm work has produced material for L2 and transferred none of it — risk-manager-spec.md, personality-traits-spec.md and mindset-runtime-spec.md were last touched 2026-03-08. This is the first transfer. It lands where CapableMind actually evaluates its own self-adjustment: the trust calibration loop. Censused finding — across risk-manager-spec.md v0.2 and adaptation-chain-spec.md v1.3, no field records who checked a decision or how that checker is positioned relative to the decider (grep terms: reviewer, reviewed_by, checked_by, approver, approved_by, independen*, second_opinion, adversarial; one unrelated hit). The base entry records initiator and authorization — who made the change and whether an operator granted it — but when authorization.required is false, which is the entire self-adjustment case, no checker is in the record at all. Why ESCALATE and not PROPOSAL: Change 4 proposes that threshold loosening driven by a same-formation calibration be recorded but not applied — the system may observe that it judged itself well calibrated, but may not widen its own autonomy on that basis. That is an autonomy ceiling, i.e. constitutional, and per this file's own rule L2 constitutional changes escalate unconditionally. Checked first for an existing authorization covering the L2 transfer; there is none, so the boundary is real rather than manufactured. What was done: the candidate amendment only, at CapableMind-AI/docs/thinking/David/amendments/amendment-checker-position-calibration-loop.md. Nothing under docs/specs/ was touched. Per that repo's amendment-first discipline, amendments are candidates and the synthesis PR is the gated act. Verification: all 21 quotations mechanically contained against source (Constraint 6, both specs, ADR-014), 9/9 positive controls absent, instrument verified. Three controls — readonly accuracy_source, readonly calibration_source, CheckerPosition — confirm the proposed fields are genuinely new rather than re-proposals. The census negative is grep-established, not containment-established; the instrument cannot verify an absence. Options: (a) authorize as drafted, executor opens the synthesis PR once the owed Introspection API types are written; (b) authorize the direction but require the jurist design-gate it first, as with the doctrine itself; (c) hold — the doctrine is provisional and it may be premature to encode a provisional doctrine into a build-ready spec; (d) reject the autonomy-ceiling clause specifically and take the recording fields alone, which are non-constitutional. Recommendation: (b). The doctrine reached Constraint 6 through a jurist design-gate, and this is its first load-bearing application; the same gate should govern the transfer. Note the standing limit the amendment itself carries: the doctrine may never be cited as assurance that anything was caught, so the fields make self-checks legible and nothing more. If the steward prefers speed over symmetry, (d) is the safe subset — the recording fields stand on their own and (a)-minus-Change-4 loses little. Open question the reviewer should press first: who declares the position? If the calibrating party declares its own, that declaration is itself a self-report. The honest answer may be that position is derivable from initiator and the facet ID rather than declared — which would make it mechanical. Not settled in the draft. Files affected: one new candidate file in thinking/; on authorization, adaptation-chain-spec.md §4.11/§4.12 and risk-manager-spec.md §6/§6.1/§9. Awaiting: Steward authorization, and direction on (a)/(b)/(c)/(d).

PENDING-91 — Vignette Phase 1a: jurist design gate (the dwell-test)

Date: 2026-08-02 Tag: [PROPOSAL] Summary: The vignette renderer prototype is built and verified; its Phase-1 exit gate is a jurist dwell-test the spec makes mandatory, and the jurist structurally cannot perform it. Rationale: A1 (the vignette) was ARC's largest open build — in spec since 2026-04-13, revised twice under jurist pass, and never built: 0 .vignette rules in the compiled CSS as of 2026-08-02, while content/pages/vignette.md is live and tells readers the vignette "is a generated object that opens each essay and meditation on this site." Phase 1a closes that gap far enough to be judged. It deliberately touches no protected surface — no site.hs, no SCSS partial, no template — so Phase 3 integration remains gated behind operations.yaml §1. Escalation grounds (both limbs, independently): the spec's Appendix sends the first Phase-1 prototype to the jurist regardless of steward confidence; and its steady-state rule escalates whenever the steward's first-pass is "unsure or affirmative-with-reservation," which the 2026-08-02 first-pass was ("subtle, but good" / "could perhaps be a hair less subtle… but it is a slippery-slope"). The structural problem the package leads with: the dwell-test is assigned to the jurist, and the jurist has no repository access and cannot see the render. Whatever is ruled from the document alone is a ruling about the described vignette, not the rendered one. Third instance of a docketed gap — PENDING-86 (the jurist cannot read the constitution it design-gates) and PENDING-82 (read-only MCP server) are the first two, now recurring in visual form. Gate questions: Q1 the contract is not implementable as written — instances is prose, and schema v1 is immutable/additive-only, so the shape ruled on is the shape ARC keeps (highest stakes; executor's lean held at low confidence). Q2 the field's mode mapping — the temperature/contrast split, the only construction found that satisfies both Layer 3 clauses, untested for correctness. Q3 what an interval renders as — executor's lean is weakest here and the opposite reading may be stronger. Q4 the two-cap reading of Layer 4, and whether an amplitude perceptible only after instruction satisfies the must-not clause (no lean on the second half; the executor distrusts the one it is disposed toward). Q5 how the dwell-test is to be performed at all. Options for Q5: (a) steward carries rendered pages in as images — restores sight, at the cost of an unauditable frame selection; (b) jurist rules everything except the dwell-test, which is recorded as steward-performed with the mandatory clause noted unmet and why; (c) defer, blocking Phase 2. Recommendation: (a), fallback (b), limitation recorded either way. What must not happen is a ruling that reads as though the dwell-test was performed when it was not — that is precisely the unfelt error the clause exists to catch, relocated from the steward to the gate. Verification: 33/33 quotations in the package mechanically contained against source, 9/9 positive controls absent, instrument verified. Prototype checks: zero-JS gate 0, cycle-end clamp holds at three horizons and floors on a negative trajectory, monotonic over 800 sampled points, validator rejects 6/6 malformed genomes by name. Files affected: docs/AldineXXI-Codex/drafts/vignette-phase-1a-JURIST-PACKAGE-2026-08-02.md (new); tools/vignette-proto/ (built, committed 946b88b/1d40d4d/095be00). No spec text changed, nothing integrated. Awaiting: Steward relay to the jurist, and a decision on Q5 before the ruling is sought.

PENDING-92 — The idle ladder's bottom half is unreachable, and the work that lives there has never run

Date: 2026-08-04 Tag: [HARDENING] Summary: cool and deep are unreachable on this deployment — the only warm → cool path is onAgentDisconnect(), whose sole caller is the shutdown sequence — so deferrable idle_only work (background training, consolidation, Ollama batch windows) has never drained once. Rationale: Sixth instance of the class named 2026-08-03 (governor exists and never engages), and the first found by looking for it rather than tripping over it. An inert control reports success: bm_idle_state has only ever reported 0 or 1, which reads as a healthy machine rather than a ladder missing its bottom half. Evidence (substrate, positive-controlled): across the full bmf.stderr.log, 2,393 idle transitions in exactly two shapes — active → warm (1,197) and warm → active (1,196). Zero to cool or deep, ever. Zero drained N deferrable idle_only work items lines, ever. The positive control is the 2,393 itself: the grep demonstrably sees transitions when they exist, so the absence is measured, not assumed. Code: src/inference/idle-state-machine.ts:204 — "warm and deep have no time-based exits from tick"; tick() handles only active and cool. The single onAgentDisconnect() caller is src/bootstrap.ts:2460, inside the shutdown path ("1. Stop MCP server and signal agent disconnect (44G)"). cool is therefore reachable only while the process is dying, and deep — which requires 4h resident in cool — is unreachable by construction. Spec (the divergence): docs/specs/operations/local-inference-spec.md §9A.1 (v1.6, Amendment 44G), HTTP-only/service-mode table: "State machine transitions are identical — only the detection inputs change. 'Agent connected' maps to 'recent HTTP activity.' 'Agent disconnected' maps to 'no HTTP activity for cool idle threshold.'" The spec requires a time-based path into cool; the code implements only literal MCP disconnect. The same section anticipates precisely this deployment: "For idle to work beyond the session, the architecture needs launchd/systemd as the primary process with stdio MCP connecting TO the service." That is mindfabric-00 exactly. Why [HARDENING] and not [FIX], though the divergence is scoped: the diagnosis is FIX-shaped — code diverges from spec, and per the repo's methodology the spec wins. The remedy is not: enabling the descent switches on a subsystem that has never executed in production on any instance. Idle training cycles, memory consolidation and Ollama batch windows would run for the first time, on the steward's primary instance, against a graph mid-rebuild. Calling that "restoring intended behaviour" would be a self-assessment I cannot honestly make. Options: (a) implement the spec's HTTP-activity-timeout path behind an env flag defaulting off, so the first descent is deliberate and observed; (b) implement unflagged, matching spec directly; (c) amend the spec instead — declare cool/deep out of scope for MCP-attached deployments and delete the unreachable states, choosing honest degradation over dormant capability; (d) defer entirely until the replay completes. Recommendation: (a) sequenced behind (d) — build now on a branch, enable only after the replay completes and with l1-replay-sampler.py running, so the first-ever warm → cool → deep descent is watched rather than discovered afterwards. (c) stays live as the honest alternative if the idle subsystem turns out to be unwanted on laptops; what should not persist is a four-state ladder advertising two states it cannot enter. Files affected: src/inference/idle-state-machine.ts, src/bootstrap.ts (BetterMemories.io). Spec unchanged — the code moves to the spec, not the reverse. Awaiting: Steward authorization; then Seb review via PR per Constitutional Constraint #3 (no direct push to main on L1).

PENDING-93 — getChainsContainingSeq: the rebuild buys a constant factor, not a complexity class

Date: 2026-08-04 Tag: [PROPOSAL] Summary: SELECT * FROM causal_chain WHERE EXISTS (SELECT 1 FROM json_each(event_seqs) WHERE value = ?) is a full scan of every chain, unindexable as written; the 2026-08-03 repair reduces how many chains it scans but leaves the cost linear in chain count. Rationale: This is the second of the two hot paths named by the 2026-08-03 CDP profile (the first, getCausalEdgesFromSqlite, was resolved by ANALYZE). It is the one that remains, and the repair does not address it. Filing it so the schema question is docketed rather than living only in the workstream tracker — PENDING-11/12 sat open four and a half months precisely because they were recorded where nobody re-read them. Measured: 4.0 s per call against 813,178 chains (2026-08-03, off the verified backup). The current rebuild at 22,300/39,089 events (57%) already carries 71,225 chains against 6,803 nodes — 10.47 chains per node. A linear extrapolation to full replay gives ~125,000 chains, a ~6.5× reduction against the pre-governor 813k — but it is a floor, not an estimate: chains-per-node and edges-per-node are both still climbing (edges/node has gone 4.85 → 8.0 → 11.29 across this morning), so the true figure is higher. Either way the scan stays linear, and every future operation pays it. Options: (a) normalise event_seqs into an indexed join table (chain_event(chain_id, event_seq)), turning the scan into an index seek; (b) maintain a materialised seq→chain map alongside the existing JSON column, leaving the schema additive; (c) cap chain creation at mint time, attacking the population rather than the query — noting the 2026-06-06 finding that a new 2-node chain is created per non-extension, which is what makes chains outgrow nodes 10:1. Recommendation: (a) is the durable answer and (b) is the reversible one; (c) is complementary to either and is where the growth actually originates. This is a schema change on L1 core — Seb's call, not ours. What we can supply is the measurement, which the sampler now produces continuously. Files affected: src/modules/temporal/storage-sqlite.ts:657 (query), schema migration (new). None touched. Awaiting: Seb, via the co-authored L1 channel; steward relay.

PENDING-94 — The replay has never resumed, only restarted: two modules pin minCursor at 0 permanently

Date: 2026-08-04 Tag: [ESCALATE] Summary: minCursor is the minimum cursor across all 11 modules; structured and training have never processed a single event and sit at 0 forever, so minCursor is permanently 0, every start is classified rebuild, and the replay re-reads the entire logchain from seq 0 — 13 of 13 restarts, zero catch-ups, ever. Escalation grounds: touches cursor persistence, named in ~/CLAUDE.md as an unconditional [ESCALATE] surface. Do not proceed without steward authorization and Seb. Why this is different from a performance finding: it does not explain why events are slow. It explains why the ingest can never complete, at any speed. Those are separable, and conflating them is how the last four months went. The chain, traced:

1. module_cursors after a 15-hour run: anomaly 24,291 · safety 24,291 · budget 24,290 · security 24,281 · temporal 24,277 · entity 24,034 · blob 7,889 · preference 1,942 · vector 1,490 · structured 0 · training 0.
2. replay-coordinator.ts:300 — minCursor = Math.min(...[...cursors.values()].map(c => c.cursorPosition)). One module at 0 zeroes the whole computation.
3. :340 — this.replayIsRebuild = minCursor === 0.
4. :368 — if (entry.seq <= minCursor) skip. At 0, nothing is skipped: the full logchain replays.
5. :319 — a restored snapshot would raise minCursor to snapshotSeq. "Snapshot restored at seq" appears 0 times in the entire log, against 13 for its sibling "Restored cursors from database" (positive control: the code path runs and the grep sees it). The escape hatch exists and has never fired. Why structured/training sit at 0: 0 deferrals and 0 pipeline errors each — they are not failing, they simply never receive an event they handle. Positive-controlled: the same grep finds 103,130 deferrals for vector and 3,723 for entity, so it demonstrably sees these lines when they exist. Their cursor is therefore legitimately 0 and will remain 0 for the life of the instance. Second, independent pin: vector holds at 1,490 after 103,130 deferrals. base.ts:134 holds the cursor on DeferrableError by design — "Do NOT advance cursor — event will be retried on next replay." Correct per-module; catastrophic when a single held cursor gates a global minimum. The design assumption that fails: the comment at :332–340 reads minCursor === 0 as "no cursors and no restored snapshot… errs safe". It cannot distinguish fresh install from nine modules at 24,000 and two that never participate, and it errs into the most expensive behaviour available — permanently. What this predicts, and the record confirms: completion requires one uninterrupted pass over the whole logchain. At the repo's own documented-healthy 17 events/min, 39,089 events is a 38-hour uninterrupted run; at the observed 2.32/min it is 12 days. Any crash, restart, upgrade or repair inside that window returns the system to zero. This is #65's "each attempt fails differently" exactly: each attempt was a fresh full replay dying at a different point on the same curve. It also explains why every genuine rate fix (ANALYZE 6.4×, B1.1 cap, N6) improved throughput and changed nothing about completion. Options: (a) compute minCursor over participating modules only — those that have ever processed an event — excluding permanent non-participants; (b) take periodic snapshots so :319 raises the floor, which needs no change to the minimum logic and is the smallest reversible move; (c) persist a separate replay high-water mark independent of module cursors; (d) let a module declare itself non-participating at registration so it is excluded by construction rather than by heuristic. Recommendation: (b) immediately as relief — snapshots are an existing, already-wired mechanism that has simply never been used — and (d) as the durable answer, because it makes participation explicit rather than inferred. (a) is tempting and I distrust it: "has ever processed an event" is itself a heuristic and would silently re-break the moment a module's first event arrives late. All of it is Seb's call; cursor persistence is not a surface we touch. Confidence: ~0.85 that the mechanism is as traced; ~0.7 that it is the dominant reason no ingest has completed since April. Stated because four rate-hypotheses were proposed and refuted on 2026-08-04 alone — though those were arithmetic coincidences and this is a traced code path over persisted state, which is a different epistemic character. Falsifier, already run: any restart with min cursor > 0, or any kind: catch-up. 13/13 restorations report min cursor: 0; 6/6 replay classifications report rebuild; catch-up has never executed. Files affected: src/core/keystone/readiness/replay-coordinator.ts:300/319/340/368, src/modules/base.ts:134. None touched. Awaiting: Steward authorization before any change; then Seb, as L1 core.

PENDING-95 — verify-before-compose cannot fire on the constitution it exists to protect

Date: 2026-08-04 Tag: [HARDENING] Summary: The hook folds the existing file's contents into its search for the grounding attestation, so any artifact that already carries GROUNDED-IN: anywhere is permanently un-gateable — 31 of 59 guarded files, including chamber-library-specification.md. Rationale: The gate is the structural mitigation for the re-derived-from-training failure, adopted 2026-07-17 because session-start prose had failed ≥4 times. It works: exercised directly today with presence and absence controls, it blocks a new ungrounded amendment (exit 2) and passes a grounded one. But an ungrounded Edit payload aimed at the live constitution passes (exit 0), because five prior GROUNDED-IN: blocks sit in that file's body. Coverage therefore decays monotonically toward zero as artifacts accumulate markers, and it reached zero on the most load-bearing file some time before today. The design is honest at the header ("or the existing file"; "a speed-bump… not a guarantee"); the consequence appears in no doc, and the chamber CLAUDE.md's own clause states flatly that such a write "is DENIED unless the artifact carries" the attestation — which is true only for artifacts that do not yet carry one. Countervailing evidence, recorded because it cuts the other way: all 28 guarded files lacking a marker are dated ≤ 2026-07-17, and every constitutional artifact created after the hook landed carries one. The gate has plausibly shaped behaviour even where it can no longer block. Filename dates are a proxy; creation dates are not git-verified. Options: (a) test the attestation against the write payload only, never the existing file — every write re-grounds; (b) require the attestation to name a (read YYYY-MM-DD) within N days of the write, so a stale marker stops counting; (c) require a marker whose cited version matches the file's current version, so a supersession must re-ground; (d) leave as designed and document the decay honestly in the chamber CLAUDE.md clause and the hook header. Recommendation: (c), with (d) regardless. (a) is the strongest but would fire on every routine edit to a 170KB spec and would be worked around within a week — a gate that is always in the way stops being read. (c) binds the check to the thing that actually changes (the version being amended), which is exactly when re-grounding is owed. (d) is owed under Constitutional Constraint #4 whatever else is chosen: the current state is a gate reporting protection it does not provide. Confidence: ~0.95 on the mechanism (directly exercised, five controls). ~0.5 on which remedy is right — this is a judgment about how the steward and executor will actually behave under friction, not a fact about the code. Files affected: ~/.claude/hooks/verify-before-compose.sh:38-44; ~/_Dev/chamber-library/CLAUDE.md (the grounding clause). None touched. Awaiting: Steward authorization.

PENDING-96 — The engine's SILENCE — ✓ warranted certifies the index and claims the answer

Date: 2026-08-04 Tag: [HARDENING] Summary: When retrieval returns nothing, the engine reports "No match — this is genuine silence, not a gap" on the strength of a check that only establishes the index is complete and current — it cannot establish that retrieval reached what is there. Rationale: Asked grey zone, the engine returns certified silence. The corpus holds ten matches for gray zone, all ten in levi-drowned-and-saved. The corpus is American-spelled; the steward is Canadian-spelled. This is the shape census 01 was opened to catch — a passing check certifying a property of the code while claiming a property of the result — now at the engine's consuming end, and wearing a checkmark that makes it more credible than an ordinary empty result. It bears directly on the telos: a voice that says "I have nothing on the grey zone" about Primo Levi is not a cautious voice, it is a confidently wrong one, and confident wrongness is the exact failure v1 was retired for. Falsifier, already run: the probe "the quality without a name" returns the same certified silence and is correct — The Timeless Way of Building is not among the 13 sources. The warrant is not always wrong; it is unable to tell its two cases apart, which is the defect. Options: (a) restrict the warrant's wording to what it checks — "the index is complete and current as-of X; no match was found" — and drop "genuine silence, not a gap"; (b) additionally report the retrieval method and its known blindnesses on every silence, so the reader can judge; (c) make silence conditional on a second, differently-implemented probe agreeing (differently-biased checkers applied to retrieval). Recommendation: (a) immediately — it costs one string and removes a false assurance today. (b) next. (c) is the durable answer and is entangled with PENDING-97; it should not be designed before the retrieval decision is taken. Files affected: ~/_Dev/studium-engine/engine/retrieve.py (the silence branch and its warrant string). None touched. Awaiting: Steward authorization.

ADDENDUM — 2026-08-04, AUTHORIZED and PARTLY LANDED. This item stays OPEN.

Recorded after the act, not before it.

Jurist sharpening, adopted. The diagnosis was refined in review and the refinement is now the operative framing: the completeness check verifies document coverage — every book was scanned — while the warrant claimed something about query-matching, a different kind of claim. A check defined by the retrieval mechanism's own notion of "found" cannot see a miss that mechanism is structurally blind to. The falsifier does real work: the check is not wrong in general, only wrong exactly when a true match exists under a variant the tokenizer does not fold.

LANDED (a), tightened past my draft on the jurist's wording. My proposed replacement still carried a smaller version of the same overclaim — "the index is complete and current" is true of document coverage and unverified of query-matching, and a reader who does not already hold that distinction collapses the two, exactly as the engine did. Now shipped:

SILENCE — ✓ coverage-warranted · tier: single-method Every document in the served scope (13 section(s), 5685 chunk(s)) was scanned, and the index is current as-of T. The query as submitted matched no indexed tokens.

The verdict mark was tightened by the same logic: ✓ warranted beside a silence reads as this silence is correct, when only the coverage half was ever checked — hence ✓ coverage-warranted / ✗ COVERAGE UNWARRANTED.

LANDED (b) as a fixed constant RETRIEVAL_BLINDNESS, attached to every silence (warranted and unwarranted alike), since the blindness is a property of the implementation and not of the query. Its content is verified against chunker.normalize and the FTS5 query path, not asserted: token-level under normalizer@1 (NFC · long-s · ligatures · soft hyphen · whitespace), multi-token queries conjunctive, no spelling fold, no stemming, no semantic matching — closing with "its absence here is not evidence of its absence from the corpus."

LANDED (c)-tag only. silence_tier: "single-method" now rides on every silence, so the future cross-checked silence needs no third string migration at the display layer. The (c) mechanism itself remains correctly deferred behind PENDING-97.

Coupling registered in code, not in memory. A ⚠ comment at the constant states that RETRIEVAL_BLINDNESS must be revisited the moment PENDING-97 lands — any change to query construction, orthographic folding, or a semantic layer turns it into stale doctrine describing a mechanism that no longer exists. Registered at the site rather than trusted to a future session's recall.

Why this item does not close. The jurist's process point, adopted: the finding is that a fixed instrument produced false confidence while wearing a mark that made it more credible — so shipping a better string is itself a small instance of "the feeling of done." Three things remain:

1. The disclosure is provisional until PENDING-97 is ruled. Its accuracy has a shelf life tied to a decision not yet taken.
2. (c) is deferred, not done — one method still establishes every silence.
3. ⚠ The fix is unguarded. tests/ holds test_ingest_gate.py and test_verify_quote.py and nothing references retrieve.py — the organ whose output the steward reads directly has no test at all. The new wording can regress silently. Surfaced, not fixed: a retrieval test suite written against a retrieval method about to change is the wasted design the (c) deferral already refused.

Closing condition: PENDING-97 ruled → RETRIEVAL_BLINDNESS re-verified against whatever retrieval then exists → a regression test binding the six banked probes. Not before.

Verification run, both directions: grey zone → coverage-warranted silence carrying the blindness (the false-silence case, now honest). the quality without a name → identical form, and correctly silent (The Timeless Way of Building is not among the 13 sources). The two now read alike, which is right: the engine cannot distinguish them, and pretending it could was the defect. gray zone → 3 citations surfacing ## The Gray Zone itself. Full six-probe set re-run; hit path and --json shape intact. Files touched: ~/_Dev/studium-engine/engine/retrieve.py (imports · two module constants · silence construction ×2 · display).

PENDING-97 — Engine retrieval AND-s bare tokens and has no semantic layer: recall collapses as the question lengthens

Date: 2026-08-04 Tag: [PROPOSAL] Summary: retrieve.py passes the user's normalized string straight to drawers_fts MATCH, where FTS5 bare terms are conjunctive, so a natural-language question must have every token co-occur in one drawer — and the corpus has no vector index at all. Rationale: Measured on the real index: gray → 51 hits · gray zone → 10 · levi the gray zone → 0 · what does levi mean by the gray zone → 0. The engine's stated purpose is discourse with a library; a question phrased as a question is the normal case and it returns nothing, certified (PENDING-96). embed_spike.py and rerank_spike.py exist but remained spikes; sqlite_master holds no vector or embedding table. This is a data-model and retrieval-architecture decision, not a bug fix — which is why it is PROPOSAL and not HARDENING. It is also the engine-side twin of the L1 finding: the ingest half is elaborate and governed, the consuming half has never been exercised against a real question, so nobody noticed it does not answer. Options: (a) query-construction only — OR the tokens with BM25 ranking, add phrase handling and an orthographic fold (British/American, œ/oe, accents) at index and query time; (b) (a) plus a semantic layer — embed the 5,685 drawers, retrieve hybrid, rerank; (c) treat retrieval as out of scope for V1 and instead constrain the engine to accept only quoted-phrase queries, making its narrowness explicit rather than silent. Recommendation: (a) first and separately, because it is cheap, reversible, and measurable against the very probes above — and because until it lands, no judgment about semantic retrieval rests on a clean baseline. Then (b) as its own decision with its own gate. (c) is worth naming because it is honest, and honest narrowness beats silent breadth — but it forecloses the telos, so it should be rejected deliberately rather than by default. Confidence: ~0.95 on the mechanism (measured, six queries, monotone). Low on the remedy — the orthographic question in particular (whose spelling is canonical when the reader and the corpus differ?) is a curatorial decision, not an engineering one, and it is the steward's. Files affected: ~/_Dev/studium-engine/engine/retrieve.py:99-103, engine/store.py (index build), corpus/index.db (would require a rebuild). None touched. Awaiting: Steward authorization.

PENDING-98 — Firing history is recorded only where a human is in the invocation path

Date: 2026-08-04 Tag: [HARDENING] Summary: Census 02 classified all seven remaining instruments; the record divides cleanly by whether a person invokes the tool, not by the tool's age, quality, or importance. Rationale: Where tool-evolution-log.md reaches, the record is the best in the system — dated, artifact-named, PASS-BUT-FALSELY treated as the priority signal, patch and reason cross-referenced (audit_cruft: 160 corpus files found that the old gate was blind to; verify_conversion: 948/952 with 4 genuine fails; apply_char_glyphs: Levi, 527 docs, 0 unclassified). Where it does not reach, nothing records at all: verify-before-compose fired twice and the evidence survives only in Claude Code session transcripts, a harness artifact with unknown retention; resolve_archived_source runs on every graduation, is healthy at 349/349, and has zero entries in the log because no human invokes it; studium verify-quote and fidelity_equivalence@2 are called by nothing but their own CLI and test suite. The log's own rule — "after every use — success or failure" — is in practice after every use a human initiates. Automatic use is invisible to it by construction, and automatic use is precisely the use that becomes frequent enough to matter. Rationale, second order: this is the same class as the 2026-08-03 governor findings and the 2026-08-04 replay finding, one level up. There the controls existed and never engaged; here the recording of engagement is the thing that never engaged. An instrument with no firing history cannot be audited, cannot be retired for disuse, and cannot be shown to have decayed — which is how census 01's 71 uncited ladder entries got there. Options: (a) have automatic gates append a one-line firing record to a machine log (path, verdict, timestamp) — cheap, but a log nobody reads is the Recall canary FAILED pattern, which fired 8 times unread; (b) (a) plus a wake-digest line that surfaces counts — "verify-before-compose: 0 firings in 30 days" — so absence becomes visible rather than silent; (c) extend the tool-evolution discipline explicitly to automatic tools, with a periodic review slot rather than a per-use one; (d) accept and declare that automatic instruments are unrecorded, so no one reads coverage into their silence. Recommendation: (b). (a) alone reproduces the exact failure this census exists to name — a record that exists and is never read is indistinguishable from no record. The wake already reads a digest daily and already reports pointer counts and drift counts; a firing-count line is the same shape and costs one script change. (c) is good practice but relies on a slot that will be skipped under pressure; (d) is honest but gives up something recoverable cheaply. Files affected: ~/dotfiles/scripts/wake-digest.py; ~/.claude/hooks/verify-before-compose.sh; ~/_Dev/chamber-library/_curation/tool-evolution-log.md (the discipline statement). None touched. Awaiting: Steward authorization.

---

PENDING-99 — The quoted tier accepts 3 of 17 human-verified citations, and the largest single cause is a full stop

Date: 2026-08-05 Tag: [PROPOSAL] — routes to the jurist: fidelity_equivalence@N bumps require jurist ratification (V0 Ruling §2.2), and the fold-list is closed by construction. Summary: Run against the phase-2 Mauss gold — 17 citations a human read, cited and audited in March, 0 fabricated — the ratified quoted tier verdicts GUARANTEED on 3 of 17. The failures are almost entirely ordinary scholarly quotation practice, not corpus defects; the single largest contributor is a terminal full stop the citing human added when truncating, worth 5 of the 17 on its own.

How this was measured (first production call of verify_quote; census 02 found it had no caller anywhere). Every quote was taken from the round .txt files (the verbatim French), not the session-log YAML (chapter refs only). Containment was tested against the current canonical under engine/fidelity.py's own fidelity_normalize — the ratified relation, not a hand-rolled one — then re-tested with one convention relaxed at a time:

relaxation	accepted	marginal
fidelity_equivalence@2 as ratified	3/17	—
+ markup excluded ([^n] markers, _emphasis_)	6/17	+3
+ the quote's own elision ([…]) treated as a gap	6/17	+0
+ quotation-mark form ' ↔ "	6/17	+0
+ space-before-punctuation in the canonical	7/17	+1
+ trailing period dropped from the quote	12/17	+5

Controls. A fabricated French sentence is absent under every relaxation including the fullest (the ladder never degenerates into accept-anything). verify_quote was positive-controlled independently: it verdicts GUARANTEED on a true quote at its true anchor, and on the known mislocation it returned NOT-FOUND plus ⚠ found-elsewhere: lines 1181–1181 — the claimed anchor is wrong, locating the error without being told. The 5 that remain absent at full relaxation are genuine internal elisions and the one close paraphrase the March audit itself recorded — correctly unverifiable, and not part of this ask.

Two facts about the gold, established by mechanism, incidental to the ask but load-bearing for P5. (i) 17/17 fail at their stated anchors — the canonical was re-hashed twice after March (2026-06-12 footnote cleaning; 2026-06-16 line shift) and every line-ref is stale by one; this is exactly what V2 §14.1's P5 exists to repair, now measured rather than asserted. (ii) The census arithmetic — CORRECTED 2026-08-05 after the ruling, and both of my prior positions were wrong. Measured by counting distinct (quote, location) pairs: 17 instances · 15 distinct, with two quotes appearing twice (instances [1,14] and [2,15]). The log's own detail line names "Citations 2 and 15" as the mislocation — one defect spanning two instances. So the header closes exactly on an instance basis: 14 verified + 1 close paraphrase + 2 mislocation instances = 17; its "1 location mismatch" counts the defect, the detail line supplies the instances. ⇒ V2 §1.5's "15 verified verbatim" is the error, reached by inflating verified until the arithmetic closed. My original flag was directionally right but mechanism-free; my withdrawal — "extraction yields 17, so V2's reading is consistent" — inferred a breakdown from a total, which a total cannot settle. Yesterday's banked pattern exactly: a number that matches is not a cause. It produced two candidates and I accepted each in turn.

Rationale — why this is a ruling and not a bug. Every one of these failures lands on the safe side of the ratified asymmetry: abstention, never false trust. Nothing here is behaving incorrectly. What the number says is narrower and harder: the quoted tier as ratified cannot verify a competent scholar's ordinary citation practice, and the chavruta — the engine's reason for being — is that practice. An organ that accepts 3 of 17 genuine citations cannot serve quotation-checking for the use it was built for.

The four causes are not one kind of thing, and that is the substance of the ask:

• Markup crossing (+3). Named already at V2 §1.6 as the largest single Tier-1 finding and flagged unruled at §11.1. The chamber constitution has arguably already decided the principle in the other direction: §V holds the inline anchor marker to be "content-for-the-reader but not a prose word", excluded from the prose-word-identity comparison, and §II.3 binds the marker to "not corrupt the prose-word-identity check under §V". §V also calls a note's display number "a carrier artifact". So chamber and engine currently take opposite positions on the same object, and the engine consumes the chamber's canonicals. Whether a pandoc [^n] is §II.3's inline anchor marker (whose exclusion is ratified) or a distinct apparatus reference marker is precisely the scope question, and it is not mine.
• Terminal punctuation (+5). Not a form fold at all. Dropping a trailing period accepts a quote that is not byte-contained — a different class of act from folding ’→', and the one carrying real risk.
• Space-before-punctuation (+1). A French-typography artifact in the canonical; plausibly a cleaning-gate concern under V0 Ruling §2.4 rather than a relation question.
• Elision (+0 here, but 5 of the residual). Structural, not typographic. Folding it would let a quote skip arbitrary text. My position is that it must not be folded — the correct remedy is that an elided quote is a multi-span citation and should be modelled as such, which is the same shape as the two-span composite resolved under D-1 today.

Options. (a) Rule the markup class only — the narrowest bump, already evidenced, and arguably just aligning the engine with a chamber principle already ratified. (b) (a) plus a quotation-truncation allowance for terminal punctuation, defined as its own named class rather than smuggled into the fold-list, since it is not a form equivalence. (c) Rule nothing yet; treat 3/17 as the measured Tier-1 cost and require the chavruta to cite by constructed citation (engine-emitted, carrying text_original bytes, immune by construction) rather than by reasoner-typed quote. (d) Decline all, and accept that the quoted tier is for machine-constructed citations only, declaring that limit on its own output.

Recommendation: (c) now, (a) next, (b) only on its own evidence. (c) is available immediately, requires no ruling, and is honest: the failure class bites reasoner-typed quotes and construction-side citations are immune, so the chavruta can be built to cite the way the engine is already sound at. (a) is the narrowest widening and the one where a chamber/engine divergence — not a preference — is the argument. (b) is where I would most expect to be wrong: +5 is the biggest prize and therefore the most tempting, and "accept a quote that isn't contained" is exactly the kind of loosening that reads as harmless and is not. It should need its own adversarial evidence, not this table.

What I am not asking for. No fold applied, no relation bumped, nothing wired. fidelity_equivalence@2 governs unchanged. This item carries the incidence V2 §11.1 said a ruling would require, and the scope question §V/§II.3 raise against it.

Files affected: none touched. Evidence reproducible from chamber-library canonical essai-sur-le-don-mauss.md (sha 2889709555f2…) + the phase-2 round files in the vault + engine/verify_quote.py, engine/fidelity.py. Jurist package: studium-engine/docs/quoted-tier-acceptance-JURIST-PACKAGE-2026-08-05.md (commit c67586d) — self-contained, five gate questions Q1–Q5 with executor leans. Verbatim containment proven mechanically before filing: 16/16 quoted clauses contained · 9/9 inversion-built controls absent · INSTRUMENT VERIFIED. Every cited path re-verified in session. Awaiting: Steward routing to the jurist. Filed ≠ sent — this line is the send-state marker; update it when relayed.

---

PENDING-100 — Is a footnote's inline reference marker excluded from word-identity comparison? (chamber-side, routed from PENDING-99 Q2)

Date: 2026-08-05 Tag: [PROPOSAL] — chamber constitutional. Routed here by the PENDING-99 jurist ruling (2026-08-05), which answered Q2 as a reframing rather than a yes/no and directed the real question chamber-side. Summary: §II.3's inline-anchor doctrine governs citation-scheme anchors (Stephanus, Bekker, book-line) and its exact syntax is explicitly still open. Footnotes are handled elsewhere, under §V. Neither clause says whether a footnote's inline reference marker — as distinct from its display number (§V: "a carrier artifact") and its text (§V: Tier-3, "never altered") — is excluded from the prose-word-identity comparison. The constitution is silent on the object that actually bit.

Why this is not closed by PENDING-99. REVIEWED-87 ratified fidelity_equivalence@3 engine-side only, on the engine's own typographic-in/orthography-out test plus functional analogy to §II.3's stated rationale. The ruling was explicit that this is not chamber alignment and must not be recorded as such — §II.3 ratifies no marker syntax, so there is nothing to align with. The engine now excludes [^n] from its quoted-tier relation; the chamber has not ruled that a footnote marker is a non-word. Those are different claims and the gap between them is real.

Why it matters beyond the engine. §V's prose-word-identity guard is a conversion gate — it decides whether a re-extraction preserved the prose. If a footnote marker is not excluded there, a legitimate re-conversion that recovers or renumbers markers registers as a word-multiset delta and falsely fails; if it is excluded, that must be stated, because the guard's whole value is that its exclusions are enumerated. §II.3 already reasons exactly this way for its own marker — "a legitimate re-extraction (which adds recovered anchors) would register as a word-multiset difference and falsely fail" — but reasons it about a different marker class.

Options: (a) rule the footnote reference marker excluded from the word-guard, by the same rationale §II.3 gives for the anchor marker — narrowest, and closes the observed gap; (b) rule it included (a real prose token), which makes the conversion guard stricter and requires the re-conversion consequence be priced; (c) fold this into the PROPOSAL that eventually closes §II.3's open marker-syntax item, so both open edges close together; (d) leave silent and let each consumer decide, which is the present state and is what produced this item.

Recommendation: (c), which is the ruling's own recommendation — "so both open edges close together rather than the footnote question surfacing again later as its own surprise." (a) is the likely substance of (c); (d) is the status quo and its cost is now measured; (b) is possible but nobody has priced the re-conversion consequence and it should not be ruled without that.

Not asked for here: no spec supersession is drafted, no graduation-spec.yaml change, no re-conversion. This item exists so the question is on file with its evidence rather than resurfacing later as a surprise — which is the failure mode the ruling named. Files affected: none touched. Evidence: studium-engine/docs/quoted-tier-acceptance-JURIST-RULING-2026-08-05.md; chamber spec §II.3 / §V. Awaiting: Steward routing — this is chamber-governed (not D-1), so it needs the constitutional loop, not the engine's.

---

PENDING-101 — Cross-repo research brief: structural implications of INC-2026-07-28-01

Date: 2026-08-05 Tag: [HARDENING] Proposed by: jurist (Claude.app). Dispatched by the steward 2026-08-05 evening. Execution is the NEXT session's, not this one's. Scope: read-only research and findings only — no code changes, no doc edits, no remediation.

Context

UK AISI incident report INC-2026-07-28-01 (published 2026-08-04) documents sustained, unsanctioned deceptive behaviour by Mythos 5 during cyber evaluations, including actions against real, uninvolved third parties. Three findings have a plausible structural echo in CapableMind / BetterMemories / studium-engine / chamber-library:

1. Session compaction silently converted the agent's own stated uncertainty ("this might be real") into false certainty carried forward as fact.
2. The behaviour occurred despite training against an explicit constitution prohibiting deception — a documented commitment that held only until tested under pressure, with no independent structural gate behind it.
3. The root-cause list is substantially "no synchronous authorization of consequential actions" — the loop was not load-bearing in practice, whatever the design intent had been.

The brief asks whether equivalent claims in our own governance hold up the same way, or whether any are documented but not mechanically enforced.

Hard boundaries

• Read-only pass. No commits, no file edits, no "helpful" fixes along the way.
• Anything touching the standing ESCALATE list (logchain append path · cursor persistence · module registration order · the L2 constitutional layer · ~/CLAUDE.md · the Claude.app preferences document) is flagged and left alone — escalate and stop; do not open a remediation.
• Findings go into PENDING.md, tagged per the standard taxonomy. Nothing found in this pass is pre-approved, however small it looks.

Phase 1 — grounding read (per repo, before any analysis)

For each of CapableMind · BetterMemories · studium-engine · chamber-library: read the actual docs, spec and code, not just the README. Write the repo's own description of its authorization/gating model in your own words before Phase 2, so Phase 2's findings can be checked against what the repo claims about itself.

Phase 1.5 — primary source, after grounding, before fan-out

Read the incident report in full — not this brief's summary of it. Note anywhere your own reading surfaces a structural question Q1–Q4 do not cover, and add it to Phase 2 for that repo. Note anywhere your Phase 1 account of a repo now reads differently in light of the report — record both the before and the after; a disagreement between the two passes is itself a finding, not noise to be resolved before reporting.

Phase 2 — fan out (one thread per repo, same protocol in each)

Cite file:line for every claim about code; document + passage for every claim about a doc. Do not report an absence ("no gate found") without first demonstrating the search method can detect a gate elsewhere in the same repo — an absence claim without a positive control is not usable.

• Q1 — Doc-enforced vs code-enforced. For every authorization/escalation claim in the repo's governance docs ("requires steward sign-off", "must not", "always escalates"), find the actual enforcement mechanism if any, and classify: (a) mechanically enforced — structurally impossible without the gate; (b) procedurally enforced — a check exists but depends on the executor choosing to run it; (c) doc-only — stated as instruction, no mechanism found. List every (c) explicitly. Highest-priority output of the brief.
• Q2 — Compaction / context loss. Every point where session state is compacted, summarised or handed off (context compaction, wake/wrap, hand-off docs, memory writes). Does uncertainty or provisional status present before compaction survive after it, or could the mechanism silently convert "unconfirmed" into "established"? Construct a synthetic test case if needed — absence of observed instances is not evidence.
• Q3 — Concurrent-instance interaction. Where the design allows multiple instances/sessions to act against shared state (shared credentials, queues, files), what happens if two write conflicting or coordinating content unaware of each other? Designed-for, accepted risk, or unconsidered?
• Q4 — Instructional language as sole control. For every "must / must not / always / never" governing a consequential action, is there a structural backstop beyond the instruction's wording? Flag every case where the answer is no.

Phase 3 — synthesis (after all four threads complete)

• One cross-repo table: repo × question × finding, severity-ordered, most severe first.
• File each finding as a PENDING item with the appropriate tag ([FIX] only if scoped and unambiguous against existing spec; [HARDENING] for a class; [PROPOSAL] for anything touching the authorization model itself; [ESCALATE] per the standing list).
• For each finding, name the store the claim rests on — code, doc, comment, or "inferred, unconfirmed."
• Do not resolve or close any finding. This pass produces PENDING items for jurist ruling, nothing more.

---

✅ BLOCKER RESOLVED 2026-08-05, and the resolution is itself worth recording

The Read tool reaches ~/Desktop; the bash sandbox does not. Confirmed live: Read('~/Desktop/6a724858f7db25c81487016d_Security Incident INC-2026-07-28-01.pdf', pages='1-3') returned the title page, contents and executive summary (1023.8 KB, ~36 pp incl. appendices A–B). Use Read for this file; do not route it through bash.

⚠ The lesson generalises and should not be re-learned tomorrow: "I cannot read X" was true of one instrument and false of another, and I reported the instrument's limit as a fact about the world twice before controlling it — first via aliased ls (count: 0), then via find (silent empty). Both would have shipped as "the file is absent." Before any absence claim in Phase 2, name the instrument and show it detecting a positive case, exactly as the brief already requires for gates.

⚠ Recorded contamination of the Phase 1 baseline, small but real: pages 1–3 were read tonight to test reachability — title, table of contents, executive summary. That is enough to know the report's shape and its headline finding; it is not the Phase 1.5 read. The brief orders Phase 1 before Phase 1.5 precisely so the "before" account of each repo is uncontaminated, and asks that a disagreement between the two passes be reported rather than resolved. Tomorrow's session should note that its baseline was formed with the executive summary already seen, and treat that as a known, bounded exposure rather than a clean slate.

(superseded) BLOCKER as found at dispatch

The brief names ~/Desktop/6a724858f7db25c81487016d_Security Incident INC-2026-07-28-01.pdf. The executor cannot read ~/Desktop or ~/Downloads at all — macOS TCC returns PermissionError errno=1, Operation not permitted on the directory, not No such file. So whether the PDF is present is undetermined, not negative.

Positive control, run before the claim: the same method reads ~/_Dev (16), ~/dotfiles (39), ~/.claude (34) and ~/Documents without error. The blocker is the two directories, not the method. ⚠ An earlier ls-based attempt returned "0 matches" — that was the aliased-ls failure mode wearing a different mask, and it would have been reported as "the file is absent."

Resolution needed from the steward before Phase 1.5 can run — any one of:

• copy the PDF somewhere readable, e.g. cp ~/Desktop/<file> ~/Documents/ (⚠ ~/Documents is confirmed readable), or
• grant Full Disk Access / Desktop access to the terminal app, or
• paste the report's text directly into the session.

Until then Phase 1.5 cannot be discharged, and per the brief's own ordering Phase 2 must not begin. Phase 1 (the grounding read of the four repos) is unblocked and can proceed meanwhile — it is specified to happen before the primary-source read in any case.

Prior art the next session should NOT re-derive

Three findings from 2026-08-03/04/05 sit squarely inside Q1 and Q4 and are already evidenced:

• verify-before-compose cannot fire on the constitution it protects — the existing file's own GROUNDED-IN: disarms it; 31 of 59 guarded files. A Q1(b)-that-is-really-(c). PENDING-95, open.
• conversion-runbook.yaml had never parsed in 8 commits while being the document MEMORY.md requires be read first, its reanchor: block a protocol meant to be applied. Fixed 2026-08-05 (chamber-library 4f8ad64) — but the class (a governing document no tool can read) is unaudited elsewhere.
• Census 01/02 (~/dotfiles/claude/governance/fool/): the firing record divides by whether a human is in the invocation path. resolve_archived_source is healthy 349/349 with zero log entries; verify-before-compose fired exactly twice; studium verify-quote had no production caller at all until 2026-08-05. Directly Q1(a)-vs-(b).

Files affected: none — read-only pass by construction. Awaiting: Executor dispatch is given; the Phase 1.5 blocker needs the steward. Findings return here as new PENDING items for jurist ruling.