dotfiles/claude/memory/MEMORY.md

name, metadata, permalink

name	metadata	permalink
	node_type title type permalink originSessionId memory MEMORY note claude-memory/memory 22915403-bc5d-4796-9c7d-196b7c30d2f9	claude-memory/memory

Claude Code Memory

Standing preferences

• 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).
• 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 — the type masters (Bringhurst/Tschichold/Hochuli/Lupton/Sousa, ~20-21 sources) live in a dedicated MemPalace at ~/.mempalace/palace-chamber-typography; query with mempalace --palace <that> search "…" (CLI, NOT the MCP tools which point at palace-memory). For ARC typography work — don't re-ask where it lives.
• 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.
• MemPalace KG object 128-char cap — kg_add object hard-caps at 128 chars; write KG objects as short keyword phrases on the FIRST pass, detail goes in the drawer. Recurs at every /wrap-up §5 — stop re-deriving it.
• 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 sessions from here on, but very concentrated. Favour ONE tightly-scoped high-leverage bite taken all the way to a committed/verified stop, then wrap — over long multi-thread marathons. Pick the concentrated station; hold the rest as ranked horizons.
• Constitution-as-block, then pull-based corpus — steward discipline (2026-07-14, named out of real frustration at thread-fragmentation): work in BLOCKS — finish the constitution as one established block FIRST, THEN corpus-into-spec piece by piece, PULLED by what each engine phase needs, not certified wholesale. Substrate need not be wholesale-trustable, only trustable for the phase in hand. Bounded question → bounded answer; do NOT surface N new threads alongside it (that's the mining-in-many-directions that discourages him). Hold deferred findings in the block's tracker; keep his open-thread count LOW. The higher-order sequencing discipline above feedback-shorter-concentrated-sessions.
• Checkable claim surfaces bugs — insisting on a checkable claim (a number, a substrate-verified fact, a discriminating test) instead of a soft classification repeatedly EXPOSES a real bug, not just the asked-for figure; the demand for verifiability is itself a defect-detector. Never force a figure onto a comparison that can't bear it — name the actual problem. Steward-named 2026-07-13 ("five times in one day; not coincidence").
• Completion is a tripwire — the feeling of "done" (esp. after fluent output) is the cue to verify the tail (census/gate/scan-check), not the signal to ship; the last 10% (where trust is earned or faked) is invisible from inside the first 90%. Ninety-Ninety Rule as a security property; a handle on the contamination-problem + τὸ πρόσφορον threads (steward 2026-07-06).
• Studium Engine charter — the engine's constitutional doc at studium-engine/docs/the-studium-engine-architectural-charter.md. The inversion (reasoner-at-centre over a BOUNDED provenanced corpus); three cognitions; boundedness=trust; free-the-reasoner/tighten-the-verifier; CapableMind's governance thesis on a library. Read before building the engine.
• Studium Engine = Sixtus-V craftsman collaboration — work the ground freely (steward describes vision; I build, surface only vision-forks); constraint-candidates = 3rd governed instrument (Bach principle: constraint unlocks mastery; absence of a constraint-proposal is itself a drift signal; I name, steward applies). Studium-engine only; heavier loop holds 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.
• Verify each post type after changes — ARC: after any shared CSS/template/composition change, check EVERY content type on BOTH desktop and phone, not a sample on one viewport. Lesson from §II.d gate verified phone-only → desktop appearance surfaced 2 sessions late (no regression; just unseen). Per-type×per-viewport extension of trust-prior-pass-frame; belongs in the SCSS verification ladder.
• Reading Compass is SVG, not type — ARC Compass sigils are SVG <symbol> artwork, NOT Plex Sans / nav typeface / Pattern 3. Recurring conflation; steward corrected 2026-06-03. Plex-Sans nav text = breadcrumb + version-stamp + post-type only.
• 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.
• MemPalace wing-filter broken — wing-scoped search → 'Error finding id' (upstream #1665, open at HEAD); search UNSCOPED + post-filter by wing. Don't run repair (#1589). Affects wake-up §2.b.3.
• Skill-harvest register — canonical home for proposed skills awaiting steward authorization; the governed analog of PENDING.md for our own tooling. Full review 2026-06-05: bmf-diagnose + /pre-build-audit AUTHORIZED (build-on-need); /spec-code-audit DEFERRED (first L1 audit); /arc-typeset REJECTED (superseded by §I.k build enforcement); /vignette still deferred (Phase 2); Symmetria §3 flags + verification-ladder BUILT same evening.
• 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 — NOW CENTRAL to the steward↔Seb workflow (est. 2026-06-02): app.plane.so/capablemind, BMF project, thin effort-tasks [BM #N] over canonical GH issues (effort-only, no technical detail; labels/priority mirror GH; issue attached as link). Executor keeps task state current as the 6-hour relay. ⚠ BBF = BetterBridge product, NOT the board. Plane MCP user-scoped/OAuth; load tools via ToolSearch select:mcp__plane__*. create_work_item needs description_html.
• 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.
• 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 clarifying the chamber's telos: fidelity-without-trust, reading-is-unsolvable-and-that's-the-feature, language-as-notation, L2/engine=answerable-not-pure. Read when the thread touches the engine's purpose; 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.

• MemPalace wind-down — DECISION (steward, evidenced 2026-07-07): wind down the palace-memory MemPalace instance, rewire wake/wrap to the files layer; EXECUTE FRESH. KG already exported+secured (knowledge-graph.jsonl, 329 triples). Typography palace KEPT untouched (separate instance). Staged plan + evidence in the file; audit detail in session-ledger-2026-07-07.md.
• 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: A–F · Stage M · Waves 0–3 · W3R · STAGE G DONE/SEALED (GPG ac0a7ee, 2026-06-10) — reactive mode governs. Open work → project-arc-open-work-register (A1 Vignette F+1 · A2 cul-de-lampe · content sweeps · Phase-2 held set). Full chronological detail lives in the tracker file; the prior 8KB inline log was relocated to MEMORY-reference.md (2026-07-06 compaction).
• 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.
• ARC chamber v1-legacy cluster — ARC's content/chamber/** is intentional v1-Chamber legacy (not drift); deferred to-do = gather into a presentable cluster as a record of development. Out of §5 clause-1 audit scope. Confirmed 2026-05-29.
• Studium engine telos — the chamber of voices — the ultimate goal, hold above the build plan: David's childhood imaginary chamber of beloved hero-voices he took counsel from → enter into discourse with his library + have the voices converse amongst themselves, this time accountably (the engine's v1 was literally "the Chamber" — eloquent/unaccountable simulacra; this is the same ambition built grounded/citable/checkable). 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. 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 — some EPUBs render diacritics/non-Latin script as INLINE IMAGES; the standard image-drop SILENTLY MUTILATES them (PASS-BUT-FALSELY). Tripwire = audit_cruft md_image count; INSPECT before dropping; character-bearing images = CONTENT (map→Unicode). (Alter's Psalms parked pending a glyph-map.)
• 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 (2026-05-15→) + the architectural charter (constitutional doc). Steps 0–7 built; corpus CLEAN. Stage-1 rebuild plan ruled 2026-07-04 (docs/stage-1-rebuild-plan-2026-07-05.md): next = V0+N0 contracts (V0 verifier = JURIST-GATED), then verifier-leads-with-interleave (V1→V4; N1→N3). Collaboration = feedback-studium-engine-sixtus-v-collaboration.
• L1 reliability — canonical L1 tracker (est. 2026-05-28). Latest (per file): N6 deploy #175 landed live + holds (multi-day wedge gone, A1″ migration live); CapableHands-as-BMF-clasp = the PRIORITY task (PENDING-41); PENDING-27 awaits jurist. L1 sits behind the Studium/chamber focus. Read the tracker at /wake-up before any L1 work.
• 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-07-14 midday — PENDING-55 positive test + residual-a FIX; jurist reviewed the whole sequence — The jurist REVIEWED the whole sequence and REFUSED the §8 batch-authorization, naming the document's own contradiction (a week of 3 steward-caught / 0 self-caught errors used to argue for LESS per-item review — the contamination gradient in governance costume). Accepted; posture restored: per-item review; §8 = register, not authorization. Ran PENDING-55 verify-flow as a POSITIVE test (not the grep the jurist rejected): the graduation gate FIRES on real corruption (Leg B: 200-word-corrupted candidate → FLAG→refused) + has no skip path at the door — and the test surfaced a real overreach the grep would have hidden: a single ABSTAIN covered both "no ground truth" (permanent) AND "V-TEXT source off-disk" (contingent), the latter proceeding without a verbatim check. Jurist ruled it a FIX to land (a false ABSTAIN is as much a lie as a false PASS): split ABSTAIN (permanent, tier-level→proceeds) vs UNVERIFIED (contingent, run-level→HOLDS). LANDED + tested + committed — dbcdcc0 (FIX) + 632057b (doc-currency); 119/119; 2 commits unpushed (steward's Gitea/push call). Other rulings recorded (dotfiles PENDING-55): residual-b→PENDING-58 precondition; PENDING-56-fallback dormant; datum-not-ledger candidate-not-constitutional; quarantine namespace designed-not-built. Self-catch: guessed PENDING-46 was the citation-amendment home → flagged-to-verify → it's CLOSED (the flag-before-assert habit fired). ⚠ PULLING THREAD (revised by the post-wrap planning exchange — see the session file's AMENDMENT): the fork RESOLVED to the steward's block-discipline (feedback-constitution-as-block-then-pull-based-corpus, named out of real frustration at thread-fragmentation): finish the constitution as one clean block FIRST (the §6 tail — PENDING-58 rewrite + citation amendment, each own review), THEN corpus-into-spec pull-based per engine phase. Substrate findings (Eichmann DIRTY + 4712 filepos residue; V-TEXT sweep never ran; Levi=OCR+drop-cap gate) are held in project-making-sequence-source-set, Position-I-phase work, NOT active threads. FIRST MOVE tomorrow: build ONE ordered block-map (constitution → per-phase corpus) so the open work reads as a short closable list, not a cloud; keep the open-thread count LOW. chamber 632057b (2 commits unpushed — steward's push call). Read the session file's AMENDMENT at wake.

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-13: trackers re-slimmed to one-line pointers, ~20.3→<17KB.)