dotfiles/claude/memory/MEMORY.md

name, metadata, permalink

name	metadata	permalink
	node_type title type permalink originSessionId modified memory MEMORY note claude-memory/memory 22915403-bc5d-4796-9c7d-196b7c30d2f9 2026-08-17T13:20:44.481Z	claude-memory/memory

Claude Code Memory

Standing preferences

Entries keep their rule inline when they fire at a moment I would not recognize as needing a lookup; they shrink to a pointer when the trigger is loud enough that I'd open the file anyway. A ⚠ constraint always travels with the workaround it limits.

Rules that fire silently — keep these in front of me

• Fowler's rules for quotation — single quotes primary, double for nested, logical British punctuation order. All writing.
• Canadian spelling in ARC prose — centre/colour ("almost EU"). Draft all steward-voiced prose this way; corpus "center" = autocorrect drift (cleanup open).
• Close thoroughly — no frequent deferrals — frequent deferrals ARE how the cloud accumulated. Close ALL of a block that's closable-now; for the rest, name the specific dependency.
• Shorter, concentrated sessions — ONE tightly-scoped high-leverage bite taken all the way, then wrap; hold the rest as ranked horizons.
• Constitution-as-block, then pull-based corpus — finish the constitution as one block FIRST, then corpus-into-spec pulled by what each engine phase needs. Bounded question → bounded answer; keep open-thread count LOW.
• Removing a claim ≠ removing the reliance — cutting an unsupported sentence can hide the gap; the dependency survives, now invisible. Test: does the conclusion still need it?
• Derive the rule from the consumer, not the survivor — choosing between two disagreeing implementations is selection, not derivation. Derive from what a CONSUMER must do.
• Rank on fields you actually write — a consumer ranking by an evaluative field nothing populates degrades to trivial order while claiming to rank. Verify scoring fields end-to-end; prefer signals already captured.
• The central path — answerability, not purity — the contamination recursion is probably irresolvable, so bind the claims, don't certify the parties. Route by claim-type: checkable → produce the check + a falsifier; judgment → disclose standpoint in one line, decide, record; undecidable → name it open. One layer, then act — never audit the audit.
• Notes are part of the work — footnotes/endnotes are integral: KEEP+CONVERT (<sup><a>→[^N]), never drop on graduation.
• One-shot instruments are proportionate — a measurement answering a question asked once is NOT a directive violation; its counterfactual is an assertion, not a durable tool. The violation is re-writing what's already banked (rule of three → ladder). Too few promoted, not too many built.
• A checkable question over a self-authored corpus — counting events in a record I wrote is self-report with extra steps. Before leaving any question: who authored the corpus it reads, and would a different author have written it differently? Narrow until it turns on what entries literally say.
• Grounding finds my errors, not my support — three packages running, every omission cut AGAINST my own case. Ground in TWO passes: (1) what did I get wrong? (2) what already says this? Search the register for the CONCLUSION, not just the citations. ⚠ Quote from the FILE, never from the relayed message — placement adds and cuts.
• Resurface banked notes before re-deriving · Checkable claim surfaces bugs · Census by mechanism, not proxy · Completion is a tripwire · Trust prior pass frame — the five epistemic disciplines. Kernels: read the banked note before re-deriving · a checkable claim over a soft classification is itself a defect-detector · census by RUNNING the real pipeline · the feeling of "done" is the cue to verify the tail · re-run a prior verification at the scope of your extension. ⚠ Also carried as Symmetria §3 flags — two surfaces, deliberately: §3 loads only when Symmetria is invoked, so these stay here for sessions where it isn't.

Loud trigger — pointer suffices

• Chamber work: ground in constitution + charter + runbook FIRST — any chamber work or talk about it begins there (incl. reanchor:). Repo CLAUDE.mds are pointers, not state; corpus claims come from a self-tested tool, never a hand grep.
• Governance files are dotfiles symlinks — Edit/Write refuse to write through a symlink, so edit the real ~/dotfiles/… path when appending — PENDING/REVIEWED only. ⚠ That refusal is a tool artifact, not a permission check, and this note is the documented route past the only friction guarding the constitution (PENDING-107). ~/CLAUDE.md/~/REVIEWED.md/L2 = [ESCALATE], steward's hand — a jurist sign-off does not authorize one.
• Verification ladder — the named instruments; reach for the gate the claim's shape demands instead of re-deriving one. ⚠ FROZEN — REVIEWED-123 (2026-08-17): no additions, rewordings, removals or reorderings, from ANY source, whatever its authorization, until the trial is graded (N-now 60/84). Entries earned meanwhile queue in PENDING-141's owed-entries list (4 rows). Reading it is unaffected — that is the point of the freeze.
• Skill-harvest register — canonical home for proposed skills (governed analog of PENDING.md for tooling); /wrap-up §1.6 proposes, steward authorizes. Rebuilt 2026-08-07 from the archive: 154 live proposals, grouped by kind, each with an exact archive:L### pointer. ⚠ The 2026-08-01 compaction was lossless but illegible (55 scraped header rows, 95% of cells cut mid-word) — the count it advertised, 177, was never the number. ⚠ THE STROKE-2 BATCH IS AUTHORIZED BUT SHOULD NOT BE EXECUTED YET — PENDING-141. 41 rows stamped S2 are authorized (2026-07-19, execution not a ruling) and 22 are S2? (unsettled). BUT appending them triples the ladder from 20 entries WHILE a pre-registered trial is measuring whether the ladder is reached (baseline 14%, graded at 84 transcripts). Ladder size is an uncontrolled variable in that design, so executing the authorized batch would confound the only check behind REVIEWED-95's causal claim. ⚖ RULED — REVIEWED-123 (2026-08-17): AUTHORIZED (a) HOLD, on six conditions, and the freeze is GENERAL rather than S2-specific. Grading does NOT authorize the append — the batch returns for a ruling. Report N-now at every wake until lifted; 30-day review is a live DEFERRED-DECISION. ⚠ Filing new proposals now requires a declared firing moment (/wrap-up §1.6); one that cannot name it is documentation and must say so.
• Copy-paste-clean governance drafts — draft PENDING/REVIEWED blocks as plain fenced markdown; display formatting leaks into the placed record.
• Verify-before-compose hook — chamber constitutional writes are BLOCKED without <!-- GROUNDED-IN: … --> + verbatim Grounding. Don't fight the block.
• Tool review after each use — review every tool we built after each run, success OR failure. PASS-BUT-FALSELY is the priority signal. Log: chamber-library/_curation/tool-evolution-log.md.
• Every canon doc's source lives in Chamber Sources — a canonical's source = whatever resolve_archived_source returns, never the master library or a path in frontmatter. Read the banked record before calling a mismatch a defect.
• Engine sources graduate to the permanent chamber — work added for the engine ALSO becomes permanent collection unless stated otherwise; take it all the way (clean→verify→graduate→catalogue→sidecar). Never leave staged.
• Bulk indexing runs in tranches, gated on READBACK — never one multi-day mine; order by criticality; prove each tranche by reading back, not by write-success (933k drawers once stored fine and were unreadable). Steward rule 2026-05-04, learned on MemPalace, applies now to engine corpus work.
• Studium Engine charter — the engine's constitutional doc. Read before building. · Sixtus-V collaboration — build freely, surface only vision-forks; constraint-candidates = 3rd governed instrument. Studium-engine only.
• CapableHands standing authorization — M4 mini david@10.0.1.136 durably authorized for remote OCR/inference; don't re-ask (steward 2026-07-01).
• Typography palace — query via CLI — ~20 type masters at ~/.mempalace/palace-chamber-typography; mempalace --palace <that> search "…". For ARC typography; don't re-ask where it lives.
• Steward maps live in ~/dotfiles/maps — a map = an artifact David reads directly to orient. Write to ~/dotfiles/maps/, symlink to Desktop, never straight onto the Desktop.
• Plane coordination workflow — CENTRAL to steward↔Seb: app.plane.so/capablemind, thin effort-tasks [BM #N] over canonical GH issues. ⚠ BBF = BetterBridge product, NOT the board.
• MemPalace is an unaffiliated stopgap — third-party; don't conflate with BMF/CapableMind. MemPalace PRs await MemPalace's maintainers, not Seb.
• The maturation of the chamber — a dialogue — the 2026-06-28 exchange on the chamber's telos (fidelity-without-trust; reading-is-unsolvable-is-the-feature). Companion to project-studium-engine-telos-chamber-of-voices.

Canonical Workstream Trackers

Read the tracker for any active workstream at /wake-up before composing the briefing. Append substantive moves at /wrap-up — to the chronological log, not only "current state". Per feedback-canonical-workstream-tracker-discipline.md.

• Chamber as versioned releases — THE GOVERNING FRAME for all library work. The 2000-year Chamber as versioned releases with soft borders, each serving a PURPOSE; scope every library bite through this. Open decision: which purpose anchors V1. Read the file, not this line — it holds the reframe that resolved the purpose/scope paralysis.
• Studium Engine — canonical engine tracker. N0–N2 + R0 + voice_stamp built; corpus 14 sources, trilingual, fleet 9 suites / 285. fr cell all but closed — 8 grounded (1 A + 7 B), ratio_A_to_B VOID until PENDING-134 lands. ⚠ PENDING-131 (c) never bound the engine (chunker.py has char_range since Cluster A). NEXT: rule PENDING-134 — last blocker is a steward MCP restart.
• Studium engine telos — the chamber of voices — the ultimate goal, above the build plan: the childhood chamber of hero-voices, rebuilt so the counsel is accountably theirs. Why verbatim fidelity is load-bearing.
• The Chamber touchstone — the why — seven questions to test work against when lost in the trees. Read at Step 0 of any chamber work. Holds no state; does not decay.
• The Chamber vision is NOT in one place — it lives in seven sources across two repos + memory. A single home would become an eighth unless it supersedes or points.
• L1 reliability — canonical L1 tracker. BLOCKED ON SEB (PENDING-94); BMF is down and staying down. The replay has never resumed, only restarted (minCursor is a minimum over 11 modules, two never participate ⇒ every start rebuilds from seq 0). Completion is gated by uninterrupted run length, not rate. Recall never worked either (retrieval_count = 0). Read the tracker before ANY L1 work — walked past once on 2026-08-03.
• Instrument censuses — have our gates ever fired? — census 01 (has each gate a real negative instance? → decay, not construction, is the failure mode) + census 02 (has it fired at all? → the record divides by whether a human invokes it). Both pre-registered. Read before trusting any gate's silence.
• ARC open-work register — the single code-verified source of truth for what is OPEN on ARC. Read THIS for remaining ARC work, not the chronological tracker. · ARC — chronological record; Stage G DONE/SEALED (GPG ac0a7ee) — reactive mode governs.
• Source library — link + dedupe — master ebook library ~/Documents/___The Library [ePub_AWZ3]/ (2190 ebooks). GOAL: link chamber↔sources + dedupe; a real link needs EPUB/PDF internal metadata + edition-identity, not filenames.
• Sidecar typology — protocol-dependent reading-indexes — .meta.json structural sidecar = PROTOCOL-NEUTRAL (the graduated bar); reading-indexes = PROTOCOL-DEPENDENT and probably PLURAL — don't design the schema yet.
• Character-as-image hazard — EPUBs rendering diacritics as inline images are SILENTLY MUTILATED by image-drop. Mechanism built + wired; per-source glyph-maps still owed. VIEW the glyph; map to SOURCE form.
• Making sequence source set — COMPLETE against the ReadingList (reconciliation-verified). Sourced ≠ ingested. Read before any Making/studium source work.
• Studium = CM's unfettered sandbox — experiment freely on library/engine without risking CM's runtime; breakthroughs transfer back. Steward-framed 2026-07-08.
• Be (laundromat) — Skemantix startup (Seb+David) funding CapableMind's ladder; bridge, not venture. Decisions LOCKED. Pre-revenue WTP gate = renovate Pat → charge her; no new spec until it clears ⇒ nothing for executor on be.
• The Fool — a local model in the fool seat — THE ACTIVE WORKSTREAM. Trial 09 VOID (never run); programme re-aimed from the doctrine question to the deployment question. Instrument = blind A/B arm-matching, no sound control needed. Log: dotfiles/claude/governance/fool-trial-log.md. ⚠ Its subject matter (OP-02, the fault lines) lives in CapableMind-AI, its instruments in dotfiles, and nothing in CapableMind points back.
• Obsidian vault — from archive to practice — canonical vault tracker. Frontmatter Spec v1.0.0 ratified + 2 passes applied (511 edits / 268 files, pushed). ⚠ The vault is NOT a git repo — it mirrors to ~/_Dev/david-root-and-branch-vault-git. The actual goal — a capture workflow — has not been started; don't let the frontmatter tail stand in for it.
• Chamber-typography — tracker not yet established; moves live in per-session memories (2026-05-11 →) + project-chamber-cruft-restoration.md + project-chamber-typography-mining-plan-2026-05-15.md.

Active Session

🔑 PULLING THREAD — CLOSE THE FOOL. Steward 2026-08-20: complete the Fool and the Obsidian work before the fence resumes. The Fool is now one gate and two steward inputs from runnable. ✅ (1) REVIEWED-124 IS PLACED (2026-08-20, ~/REVIEWED.md L1929) — trial 09 void is in the register. ⚠ But its Q3 as placed carries the jurist's FL5 reading that OP-02 overturned the same evening; the correction is in PENDING.md and NOT in the register. (2) Enter §5's testimony in input-dependence-01-PREREGISTRATION.md — still reads [ AWAITING ]; the steward is the only party who has read all three outputs against the same documents, and recalled-after-a-result is not testimony. ⚠ The §5 slot is phrased in ONE direction ("if your sense is that it landed somewhere the other two did not") — nowhere and cannot tell have no home in it; steward's to settle. ✅ §2a added 2026-08-21 (steward-authorized, pre-gate): secondary observable — does the Fool bound its own coverage? — bare count, no threshold, no disposition. ✅ §2b + §2c added 2026-08-22 (steward-authorized, pre-gate) — second matcher question (NEAR-IDENTICAL · DEFECT-BLIND · DEFECT-ANCHORED, asked only after all N primaries are locked) + the register observation. ⚠ Drafting §2b surfaced that §4's harvest rested on an inference the measurement never makes — chance-level matching does NOT establish sameness, so the declared deliverable could have been authorized on evidence that doesn't support it. ⚠ §4 NOT amended — the artifact carries a visible §4/§2b tension, left for the gate deliberately. ⚠ The steward's cross-trial framing is HIS, not relayed (zero hits across all 4 write-ups + log) — but his trial-04 reading and fool-trial-04:39 are the same fact with opposite valence: consistency is the finding-class AND the insensitivity ⇒ H₀ reached independently by the party with least stake. (3) The pre-registration goes to the jurist's gate (sha256 7e1c146b…; 08-21 769b057b…; as-filed 08-20 d41e1d57…). ⚠ Residual coupling: the executor authored the instrument whose result bears on its own recommendation — the gate is the only check on that. ⚠ CLASS E ARRIVING LIVE — placing REVIEWED-124 makes PENDING-148 read CLOSED while the OP-02 question is live. One id, two asks; governance_state() reads headers, not Notes. This is PENDING-146's defect in real time, on today's own item. ⚠ THE SUBSTRATE OVERRULED BOTH AI PARTIES. OP-02 was openable — the jurist called it "the only document neither of us can open"; it is on disk, hash-verified. FL5 argues from Bourdieu's shared field and illusio, NOT formation. Constraint 6 asserts difference of formation — an axis FL5 never uses. So C6 neither states FL5 "more sharply" (executor) nor negates its three-party half (jurist). Corpus check, 11 docs: bourdieu/habitus/illusio 0, peirce 0, FL4 substance 0, FL3 1 — against the pre-run census's 16/20/24. The census counted topic-adjacency and over-reported the leak the executor's own recommendation rested on. ⚠ THIRD check-before-claiming instance in three days, and it is INSIDE the document reporting the second. Part IV.a propagated an inherited claim without opening a file whose hash the same package quotes three sections earlier. Propagation is the more dangerous form — an inherited claim arrives already looking checked. The jurist said "two is worth watching" before this one was found. 🎯 THE FOOL IS RE-AIMED — deployment, not doctrine. Steward's original intent: what does a different model, local on the M4, add or subtract in the fool role? The log's subject is the doctrine; almost the whole programme serves that instead. ⇒ capability confound irrelevant to seating a named candidate (but NON-TRANSFERABLE — does not answer "should there be a Fool seat"); no sound control needed (differential criterion). Jurist finding adopted: add and subtract may be ONE mechanism, so "seat it for the class, treat noise as cost" is incoherent and is withdrawn. Three dispositions fixed pre-run; the harvest runs in every branch. ⚠ Parkable: trials 05–08, D-2, reduction arm — 05–08 and D-2 have NEVER existed as documents anywhere. NOT parkable: the Q1 replacement run (a live authorization). ⏸ BEHIND THE FOOL, by the steward's own sequencing: the fence — (A) MOVE 2 (25 line-addressable blockquote runs; closable in ONE SITTING, needs no ruling), (C) MOVE 1 (fence the citation at emission, D-1, 532 spans, ADDENDUM 4's per-class control requirement), (B) THE ANSWER KEY (session-sized, gates PENDING-142; key it on ## BLOCKS not ids — PENDING-146). Citation exposure behind PENDING-131 (c) live since 2026-08-10. And the Obsidian capture — ⚠ the daily-note backup must accrete DURING the session; a wrap-triggered backup inherits the wrap's failure mode, which is exactly what 2026-08-19 demonstrated. ⚠ REPORT AT EVERY WAKE (REVIEWED-123 cond. 2) — N-now = 46/84. ⚠ COUNT WITH THE TRIGGER'S OWN GLOB, NOT find — TRANSCRIPTS.glob("*.jsonl") is NON-recursive (governance-drift-check.py:331); find recurses into subagents/ and over-counts (54 vs 46 on 2026-08-22, a false rise). Series: 60→61→47→46, still falling. Earlier framing: (60 on 08-17, 61 on 08-18, 47 on 08-19). A 30-DAY ROLLING WINDOW, not cumulative — at ~1 session/day it converges to ~30, so transcripts 84 very likely never fires and every "N remaining" report was a false countdown. Ladder FROZEN generally; 4 rows queued in PENDING-141. PENDING-147 needs a steward/jurist decision. ✅ Leg (i) discharged — 47 transcripts archived outside the pruned tree, 46/47 sha256-verified.

• Session 2026-08-20 — the Fool was answering a different question — reconstructed the crashed 08-19 session, then re-aimed the Fool. ⚠ That night's literal Q was TESTED AND RETIRED — it failed its own test (244 ledger entries, all authored by the party being measured ⇒ self-report with extra steps; see the CODA + feedback-checkable-question-over-self-authored-corpus). REPLACEMENT Q: how many corrections in the record name a DISCLOSED LIMIT as the cause? — answerable from what entries literally say. Early: n=3, and across 244 entries NOTHING attributes a catch to difference of formation. Constraint 6's mechanism is difference of bias; the record's is disclosure of scope. ⚠ OPEN, OFFERED NOT TAKEN: add a secondary observable to the pre-registration — does the Fool's output ever bound its own coverage? MUST go in BEFORE the jurist's gate. · 08-19 — the vault got a spec (RECONSTRUCTED, not wrapped) · 08-17 — the instruments audited themselves and lost.

Historical reference → MEMORY-reference.md

Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in MEMORY-reference.md — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent session-*.md files (wake §2.b.1).

Index discipline (self-bounding — keep this file lean)

Wake-loaded live index; hard budget well under the harness load ceiling. Keep to: Standing preferences · Canonical Trackers as one-line pointers (chronological detail lives in the linked tracker files, not here) · Active Session · these pointers. Rotation + budget-breach handling are wired into /wrap-up (demote prior Active Session on promote) and /wake-up (truncated load = flag + trim). Back up before restructuring. Compaction history relocated to MEMORY-reference.md at the 2026-08-20 wrap — pure history, not wake-critical.