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-07T09:58:34.188Z	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.
• 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.
• Skill-harvest register — canonical home for proposed skills (governed analog of PENDING.md for tooling); /wrap-up §1.6 proposes, steward authorizes. Compaction + ladder batch-append owed (exceeds read caps).
• 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.
• 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 (est. 2026-08-07). Steps 0–7 built, corpus gate-validated 13/13; V1 verify-quote + fidelity_equivalence@3 GOVERNING but @3 under challenge (PENDING-111, unruled). Parse fix landed 27b79ca: HIT 0/22 — the number to beat; PENDING-97 is the live blocker. NEXT: N1 → V2.
• 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.
• 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

✅ STEP 0 DONE (2026-08-07) — the MEMORY.md trim. 19.9 → 16.5 KB, verified: 0 dead pointers, 0 orphaned clauses, every dropped span has a home. Method: entries keep their rule inline when they fire silently, shrink to a pointer when the trigger is loud. Two relocations — project-studium-engine created to hold engine state the index was carrying inline, and the MemPalace wind-down entry moved to MEMORY-reference.md. Verification caught two things a fast pass would have shipped: one preference dropped by inattention (restored) and the facet-formalism pointer that lived only on the index line (relocated into project-chamber-versioned-releases). ⛔ NOW: N1, the navigation-tree builder (decided with the steward at the 2026-08-06 evening wrap; then V2). The N0 contract is written and names all four primitives — read studium-engine/docs/spec/n0-navigation-tree-contract.md §1–§2, don't re-derive. ⚠ N1 will NOT move 0/22 — that is N2. Finishing N1 with the number unchanged is the expected outcome, not a failure. ⚠ Build the tree from the READING INDEX, not by parsing headings. chamber-library/reading-indices/*.yaml carries the authoritative number→name→line map (Alexander: all 253, re-found by name, sha-bound). Heading text hits three documented OCR defects. Today's harness regex is a reference, not the input. ⏳ Not my thread: the PENDING-111 ruling (relayed 08-06 evening — sets the V-track course, does not gate N1) · the Seb package · the L2 design note · PENDING-109 census + PENDING-104 brief, both needing dates, not "later."

• Session 2026-08-06 evening — the asterisk that carried meaning — The parse fix LANDED (27b79ca): 26 crashes → 0, MISLOCATED 0, FALSE-POSITIVE 0 across all 5 items where silence is the correct answer — both deciding buckets empty, so the revert condition was not met. HIT 0/22: the engine now grounds nothing honestly, needing 13–19 terms to co-occur. 0/22 is the number to beat. ⚡ The embedding arm already scores 22/22 recall@20 on the identical items — capability measured in June, never landed; V2 is the gate that makes surfacing it safe. Governance: the register could not answer "how many rulings do I owe" (23, not the digest's 26) — REVIEWED-87→94 placed, five of them reconstructions with provenance lines; PENDING-99/-105/-106 closed (106 by split); PENDING-108/-109/-110/-111 filed. ⚡ The steward's printed A Pattern Language found that fidelity_equivalence@3 erases Alexander's invariant rating (81/114/54 across the corpus) — jurist package filed, containment 13/13. Instruments caught 4 corrections; the jurist 1; the steward 2 — and his came from reading a physical book.

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: 2026-07-17 re-slimmed to one-liners, 20.5→17.1 KB. 2026-08-07 trim (steward-directed): 19.9→~15 KB by the fires-silently/loud-trigger split, plus project-studium-engine.md created to hold engine state MEMORY.md had been carrying inline. ⚠ 17.1 KB is a prior achievement, not a derived ceiling — the real harness load limit is unmeasured; if it ever matters, measure it rather than inheriting this number.