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-02T17:10:32.010Z	claude-memory/memory

Claude Code Memory

Standing preferences

• Chamber work: ground in constitution + charter + runbook FIRST — steward directive 2026-07-28: any chamber work or talk about it begins by reading the library constitution · the engine charter · the conversion runbook (incl. reanchor: — a new hash invalidates bindings in BOTH repos). Repo CLAUDE.mds are pointers, not state. Corpus claims come from a self-tested tool, never a hand grep. Enforcement mechanism owed (hook/skill/wake-conditional; verify-before-compose is the precedent).
• CapableHands standing authorization — M4 mini david@10.0.1.136 durably authorized for remote OCR/inference; don't re-ask permission to use it (steward 2026-07-01).
• Every canon doc's source lives in Chamber Sources — a canonical's source = whatever resolve_archived_source returns (the Chamber Sources folder; NEVER the master library or a path in a plan/doc/frontmatter); read the banked source record before calling a mismatch a defect; fix wrong/missing pins to golden standard. (Steward, 2026-07-24, after 3 corrections on the Levi omnibus source.)
• Steward maps live in ~/dotfiles/maps — a map = an artifact David reads directly to orient (dashboard, corpus index, reading list). Write it into ~/dotfiles/maps/ and symlink to the Desktop, never straight onto the Desktop. Est. 2026-07-28 after one was lost and four more found unbacked; wake-digest.py reports strays.
• Governance files are dotfiles symlinks — ~/PENDING.md/~/REVIEWED.md/~/CLAUDE.md → ~/dotfiles/…; Edit/Write refuse to write through a symlink, so edit the real dotfiles path when appending PENDING/REVIEWED.
• Typography palace — query via CLI — type masters (~20-21 sources) in a dedicated MemPalace at ~/.mempalace/palace-chamber-typography; query mempalace --palace <that> search "…" (CLI). For ARC typography — don't re-ask where it lives.
• The central path — answerability, not purity — the working resolution of the contamination recursion (steward 2026-07-29): it is probably irresolvable (human bias is the other half — auditing the audit never converges), so stop certifying the parties, bind the claims. Route by claim-type: checkable → produce the check + a falsifier, motives irrelevant; judgment → disclose standpoint in one line, decide, record; undecidable → name it open. One layer of disclosure, then act — never audit the audit. ⚠ pleases ≠ achieves what's necessary — they coincide when true and welcome align; and for a tool the steward couldn't have specified, deference has nothing to defer to.
• Fowler's rules for quotation — single quotes primary, double for nested, logical British punctuation order. Apply across all writing.
• Canadian spelling in ARC prose — centre/colour ("almost EU"); corpus "center" = autocorrect drift (10 files, cleanup open). Draft all steward-voiced prose in Canadian spelling.
• Rank on fields you actually write — a consumer that ranks by an evaluative field (importance/weight) nothing populates silently degrades to trivial order while claiming to rank; verify scoring fields end-to-end, prefer signals already captured (recency). For BMF/CapableMind/studium-engine tool-building.
• Shorter, concentrated sessions — steward preference (2026-07-13): shorter but very concentrated — 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 — steward discipline (2026-07-14): finish the constitution as one block FIRST, THEN corpus-into-spec pulled by what each engine phase needs. Bounded question → bounded answer; don't surface N new threads; keep open-thread count LOW. Above feedback-shorter-concentrated-sessions.
• Close thoroughly — no frequent deferrals — steward directive (2026-07-16): frequent deferrals ARE how the cloud accumulated; close ALL of a block that's closable-now; distinguish closable-now vs genuinely-blocked (name the specific dependency, never a vague defer). Completeness complement to feedback-constitution-as-block-then-pull-based-corpus.
• Removing a claim ≠ removing the reliance — cutting an unsupported sentence can hide the gap rather than close it: the dependency survives, now implicit and invisible to every check. Test isn't "is the bad sentence gone" but "does the conclusion still need it". Earned 2026-08-02 — I reported removing a defect and had actually concealed it; the jurist found it, the kernel and four gates did not.
• Checkable claim surfaces bugs — insisting on a checkable claim (number, substrate-fact, discriminating test) over a soft classification repeatedly EXPOSES a real bug; the demand for verifiability is itself a defect-detector. Steward-named 2026-07-13. (Caught F-5 + the "finally" overclaim, 2026-07-17.)
• Derive the rule from the consumer, not the survivor — picking between two disagreeing implementations is selection, not derivation; derive from what a CONSUMER must do. Complementary-correctness defeats sampling.
• Census by mechanism, not proxy — census by RUNNING the real pipeline, not a proxy; distrust the finite-feeling bucket that arrives when you want to feel done.
• Completion is a tripwire — the feeling of "done" is the cue to verify the tail (census/gate/scan-check), not the signal to ship; the last 10% is invisible from inside the first 90%. Ninety-Ninety as a security property (steward 2026-07-06).
• Studium Engine charter — the engine's constitutional doc (studium-engine/docs/the-studium-engine-architectural-charter.md): reasoner-at-centre over a BOUNDED provenanced corpus; three cognitions; boundedness=trust. Read before building the engine.
• Studium Engine = Sixtus-V craftsman collaboration — work the ground freely (I build, surface only vision-forks); constraint-candidates = 3rd governed instrument (I name, steward applies). Studium-engine only; heavier loop for L1/L2.
• Trust prior pass frame — When extending a prior verification, re-run it at the scope of the extension. Frame-inheritance from a deep-read is contamination shape: the prior pass tested what it tested; your extension claims things it did not test. Caught 2026-05-28 → four-pass audit. Verify-before-compose at draft time, not build time.
• MemPalace is an unaffiliated stopgap — MemPalace is third-party; steward/Seb build BMF/CapableMind (hoped to replace it). Don't conflate them (3rd steward correction 2026-06-05 — the conflation even reached a skill name and was retracted); MemPalace PRs await MemPalace's maintainers, NOT Seb.
• Skill-harvest register — canonical home for proposed skills (governed analog of PENDING.md for tooling); /wrap-up §1.6 proposes, steward authorizes. Register compaction + ladder batch-append owed — it exceeds read caps (tripwire 2026-07-22). Built: /jurist-package, /model-handoff. Ruled/held detail in the file.
• Copy-paste-clean governance drafts — draft PENDING/REVIEWED placement blocks as plain fenced markdown; display formatting leaks into the placed record (REVIEWED-59 header, 07-16).
• Verification ladder — the named instruments (byte-identical compile gate, delta classification, censused-routes, fresh-clone gate, measure-toolchain-before-spec…); reach for the gate the claim's shape demands instead of re-deriving.
• 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. Detail + MCP setup in file.
• Resurface banked notes before re-deriving — when an idea was already captured (runbook known_gaps, skill-harvest, prior note), READ the note before re-deriving; re-derivation drifts (page-numbers mis-recalled as provenance vs structure-scaffolding, steward re-corrected 2026-06-27). The engine's own purpose, turned on my practice.
• Verify-before-compose hook — chamber constitutional writes are BLOCKED by a PreToolUse hook without <!-- GROUNDED-IN: … --> + verbatim Grounding. Don't fight the block.
• Tool review after each use — steward directive (2026-06-16): review every tool we built after each run (success OR failure), capture what it taught, iterate until reliable; PASS-BUT-FALSELY is the priority signal. Log at chamber-library/_curation/tool-evolution-log.md. Proven same day (audit_cruft hardening → 160 hidden-dirty files surfaced).
• Engine sources graduate to the permanent chamber — steward policy (2026-06-28): any work added for the engine ALSO becomes permanent chamber collection unless expressly stated; take it ALL the way (clean→verify→graduate→catalogue→sidecar); never leave staged. The chamber accumulates. ⇒ all ~30 Making sources graduate in.
• Notes are part of the work — steward directive (2026-06-28): footnotes/endnotes are integral — KEEP+CONVERT them (<sup><a>→[^N]), never drop on graduation. (Caught dropping Taylor's endnotes — wrong.)
• The maturation of the chamber — a dialogue — the pivotal 2026-06-28 exchange on the chamber's telos (fidelity-without-trust; reading-is-unsolvable-is-the-feature; L2/engine=answerable-not-pure). 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. Per feedback-canonical-workstream-tracker-discipline.md.

• Chamber as versioned releases (the governing frame) — steward reframe 2026-07-25: the full 2000-year Chamber (incl. image-based Warburg/Jung, Berger, Alexander) is the HORIZON; realize it as versioned releases with soft borders — "Chamber V1 = constitution vX + engine vY + a bounded voice-set, serving a specific PURPOSE" (Making Sequence · violin/XXI-century treatise · ARC). Purpose-first re-bounds the library work: the V-TEXT wave needn't all clear for V1. PENDING-75 kind-scoping = the enabler of additive version growth. Scope every library bite through this. Open decision: which purpose anchors V1.
• The Chamber touchstone — the why, and it does not move — seven questions to test work against when lost in the trees (one clause · answerable-not-pure · the seam · the gap stays open · inside-not-receiving · reading-not-concluding · for whom). Est. 2026-07-28; every quote source-verified verbatim. Read at Step 0 of any chamber work, before constitution/charter/runbook — those are operational and say nothing about why. Points at its seven sources; holds no state, so it does not decay.
• The Chamber vision is NOT in one place — honest answer to the steward's 2026-07-28 hope: it lives in seven sources across two repos + memory (one was behind a broken pointer; all pointers repaired 2026-07-28), and the two newest maps (boundedness gradient · convocation ladder = who convokes) exist only in a session record. Census + what a single home would need. Not yet proposed as a document — a grand synthesis would become an eighth scattered source unless it supersedes or points.
• MemPalace wind-down — DONE (steward 2026-07-07): palace-memory wound down, wake/wrap rewired to the files layer; KG exported (knowledge-graph.jsonl). Typography palace KEPT (separate instance).
• ARC open-work register — the single code-verified source of truth for what is OPEN on ARC (post-Stage-G, built 2026-06-11). Read THIS for remaining ARC work (A1 Vignette, A2 cul-de-lampe, content sweeps, Phase-2/held set, REVIEWED-placement debt), not the chronological tracker.
• ARC — canonical ARC workstream tracker (chronological record 2026-04-16 →). Status: STAGE G DONE/SEALED (GPG ac0a7ee, 2026-06-10) — reactive mode governs. Open work → project-arc-open-work-register (A1 Vignette · A2 cul-de-lampe · content sweeps · Phase-2 held set). Chronological detail in the tracker file.
• Chamber-typography — tracker not yet established; substantive moves live in per-session memories (2026-05-11 onward) + project-chamber-cruft-restoration.md + project-chamber-typography-mining-plan-2026-05-15.md.
• Studium engine telos — the chamber of voices — the ultimate goal, above the build plan: David's childhood chamber of hero-voices → discourse with his library + voices conversing, this time accountably (v1 was eloquent/unaccountable; same ambition built grounded/citable). Why verbatim fidelity is load-bearing.
• Studium = CM's unfettered sandbox — Studium/chamber are personal projects Seb now sees as fundamental to CM; experiment freely on the library/engine without risking CM's runtime, breakthroughs transfer back (V2 verifier = live example). Steward-framed 2026-07-08.
• Making sequence source set — COMPLETE against the ReadingList as of 2026-06-18 (reconciliation-verified); census of what's sourced where, sourced≠ingested (only Pos I in manifest), the Handke-German decision (original is source), the Levi drop-cap gate (RESOLVED STALE 2026-07-19 — initials present). Read before any Making/studium source work.
• Source library — link + dedupe — steward's master ebook library = ~/Documents/___The Library [ePub_AWZ3]/ (2190 ebooks, messy nested). GOAL: link chamber↔sources (provenance index) + dedupe; real link needs EPUB/PDF internal metadata + edition-identity, not filenames. Detail + seed in file.
• Character-as-image hazard — EPUBs rendering diacritics as inline images are SILENTLY MUTILATED by image-drop. Mechanism built (apply_char_glyphs.py, REVIEWED-70/v2.5.0), wired as a born-digital precondition; per-source glyph-maps still owed. VIEW the glyph; map to SOURCE form.
• Sidecar typology — protocol-dependent reading-indexes — TWO layers: .meta.json structural sidecar = PROTOCOL-NEUTRAL (the graduated bar); reading-indexes (rich YAML) = PROTOCOL-DEPENDENT, probably PLURAL — don't design the schema yet; settle corpus to gold, let protocols declare themselves. Steward 2026-06-29.
• Studium Engine — no tracker file yet; moves in per-session memories + the architectural charter. Steps 0–7 built; corpus CLEAN; V1 verify-quote BUILT + fidelity_equivalence@2 GOVERNING (2026-07-19; @1 frozen; dash refused/evidence-gated; Greek/Latin census owed → @3). Stage-1 rebuild plan (studium-engine/docs/stage-1-rebuild-plan-2026-07-05.md): V0+N0 ruled · V1 done → V2→V4 / N1→N3. Collaboration = feedback-studium-engine-sixtus-v-collaboration.
• L1 reliability — canonical L1 tracker (est. 2026-05-28). Baton rule LIFTED 2026-08-03 (was "do not re-enter until Seb pushes"; Seb is stuck on Peter's project, not silent by choice). Latest: the ingest mystery is solved — ANALYZE never run ⇒ boolean-index pathology; B1.1's cap works, so the defect is DATA not code; repair run, replay in flight. Remaining for Seb: getChainsContainingSeq json_each scan (unindexable, schema change). Read the tracker before ANY L1 work — this instruction was walked past once today.
• Be (laundromat) — canonical Be tracker (est. 2026-06-08). Be = Skemantix startup (Seb+David) funding CapableMind's ladder; bridge, not venture. Decisions LOCKED (entity/pricing/infra in file); a11y gate MERGED. Pre-revenue WTP gate = renovate Pat → charge her; discipline: no new spec until it clears → nothing for executor on be. Repo @ f43a0fd.

Active Session

• Session 2026-08-03 — the governors that never engaged — the inherited question answered, and it became the day's theme: controls that exist in code and never engage, invisible because an inert control reports success. Census 01 (pre-registered): fool/ strong, but drift-check 3-of-5 families INERT and 71 of 75 ladder entries cited nowhere (no IDs ⇒ firing history unrecordable). S-series closed on discovering the jurist ruled all Q1–Q5 on 2026-05-18 and the items were mislabelled 2½ months (S6/S7/S9 built · S2 rebuilt as [FIX] · S4/S5 withdrawn with MemPalace). Dormant legacy + GH swept: 22 → 10 open; #170 found undelivered since April. Steward lifted the L1 baton rule → mindfabric-00 pinned 6 days; CDP profile named it; ANALYZE never run in 4 months so SQLite preferred a boolean index over the selective one (6.4×, 99.8%→6.0%, /health silent→200 in 0.13 s). B1.1's cap verified WORKING ⇒ the defect is DATA, not code — 836k edges minted before the governors landed; the ingest was divergent, not slow (the real answer to #65). Repair run, replay in flight (~30 h). coherence_evaluated = 0 of 813,178 — not one, ever. PULLING THREAD: the replay — does it complete, and does the coherence evaluator ever run?

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; the MemPalace handoffs glance was retired 2026-07-07 with the wind-down).

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. (Compacted 2026-07-17: entries re-slimmed to tight one-liners, 20.5→<17.1KB.)