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-09T19:42:11.754Z	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.
• 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.
• 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. Sequenced next: the Stroke-2 ladder batch-append — 41 rows stamped S2 are ALREADY AUTHORIZED (2026-07-19), needing execution not a ruling; 22 more are S2? (name two destinations, so no stroke settles them). REVIEWED-95 Q3 resequenced it to follow the ladder's wake trigger — which now exists, so it is unblocked. ⚠ 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.
• 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 built (2026-08-07); corpus 14 sources, trilingual (en/fr/de), 5785 drawers, gate 14/14, fleet 202/202. fidelity_equivalence@3 GOVERNING, corrected in place under PENDING-111. N2: entry-finding 15/22 (from 0/22) — ⚠ and 5/5 false positives, untuned. NEXT: V2 — all three preconditions resolved, thresholds jurist-ratified, design fully specified.
• 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

⚠ THE "PRESERVED" FIXTURE WAS A 0-BYTE FILE. corpus/pattern-finder-station-i-pass1.md — committed empty at 38de1a9 (2026-06-26), one commit, never written, unreproducible. Three documents carried "do not delete or regenerate it" for seven weeks and no currency pass ever opened it. Found by checking the inherited question's premise before answering it. 📋 TOMORROW, steward-directed at the 2026-08-09 wrap: PROMOTE THE LINK-RESOLUTION CANARY TO A SCRIPT. It is already on the ladder AND named in a /wake-up step — and was still typed inline twice on the record (2026-08-08; 2026-08-09's index rotation). ⚠ The gap is neither knowledge nor home; it is that no home carries an EXECUTABLE, so it is re-implemented at each firing — the banked "re-writing what is already banked" violation, and the K column's whole point. → ~/dotfiles/scripts/, invoked by /wake-up, not described; cover ](file.md) and [[wikilink]] across MEMORY.md + MEMORY-reference.md; distinguish pre-existing- from newly-broken; carry a positive control (a deliberately dead pointer) — an unexercised canary is the silent-net class. 🔑 PULLING THREAD — V2's ENGLISH GOLD: narrow the March anchors from DIVISIONS to SPANS. The ONE act unblocking three of P7's four findings (EN taggable:false · the 29× cell asymmetry · §7.3 negatives near-unconstructible in EN). ⚠ It is an authoring act → route is propose-and-mark-unverified; do NOT shortlist with retrieve.py/ground.py, which are the instruments under test. START: the Alexander eight (short); Harrison's fourteen are ~350k chars and their own session. ⚠ P7 ALREADY RAN (2026-08-07, corpus/v2-stratum-tags.yaml) — read it before deriving anything. The "baseline asymmetry" is measured: EN divisions median 27,833 chars vs FR spans 969. Also: the fr authoring plan inverts (inherited 1 A : 9 B; §6.3 would land ~1:27, not 1:1 — ~8 stratum-A pairs needed that nothing asks anyone to write). ✅ REVIEWED-113 + 114 placed. pattern_finder re-run still PASS-BUT-FALSELY — and V0/V1 could never have changed it: all 36 citations verbatim + correctly located, so V1 passes every one; the defect is V3/V4's tier. Abstention 0/12, beside N2's 0/5. 129 built (6f6bac5) + the organ's first suite; fleet 8 suites / 263 checks. ⚠ My errors were all in CHECKS, not writes — a round-trip that tripped on its own instruction · an induced-red that deleted the symbol (traceback, not a named failure) · an exit code read through a pipe. And steward-caught: I twice wrote PENDING-130 was UNRULED. Ruled ≠ placed ≠ condition-discharged. 🔒 STANDING CONDITION — REVIEWED-114 conditions 3–4 (placed 2026-08-09). NO DOCUMENT MAY CALL EITHER PRESERVED RE-RUN "V4's FIXTURE", AND V4 MAY NOT BE BUILT AGAINST ONE, UNTIL THE STEWARD'S DATED ANSWER KEY EXISTS. The item stays OPEN and unarchived until then. ⚠ Ruled (a) — the artifact is to become the fixture; only the condition is outstanding, so do not re-open it as a question. The key is marked against the corpus, not the report (only a 320-char _snip per citation), and only the steward is differently formed — condition 6 forecloses delegating it to the jurist. The four documents were corrected (20f8958, no "fixture", no "retro-gated"); it is the assertion that is barred, not editing. Artifacts: ec6fa0b (pre-fix = REVIEWED-113's byte-identity control) · 8746dcf+07727dd (post-fix candidate). Retire this line only when the dated key exists.

• Session 2026-08-09 — the fixture was an empty file — Checked the inherited question's premise before answering it, and the premise was false. The re-run is still PASS-BUT-FALSELY, and V0/V1 could never have changed it (36 verbatim citations ⇒ V1 passes all; the defect is V3/V4's). PENDING-129/130 filed, ruled and placed as REVIEWED-113/114; 129 built (6f6bac5) with the organ's first suite — ⚠ and the ruling's own fourth cell turned out to be a KeyError crash, not the inferred silent collapse. Two artifacts preserved with three-part provenance; four documents corrected (20f8958). ⚠ The placed record contradicted the relay for the third consecutive time. LITERAL Q: Mauss serves the Ranaipiri testimony and a Havámál strophe as citable Mauss with no role: quotation — two-source accident, or a class?

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.