The ~/.claude/ directory was previously local-only — a machine wipe
would have lost the accumulated memory, custom skills, and settings.
This commit moves the durable parts into dotfiles with the same
symlink-to-home pattern used for CLAUDE.md, PENDING.md, REVIEWED.md,
and L2-BOOTSTRAP.md.
Preserved (symlinked from ~/.claude/* into here):
skills/audit/ — thinking-folder drift scanner
skills/symmetria/ — practice-of-return discipline
skills/vault-update-people/ — Obsidian People-file maintainer
skills/wake-up/ — session restoration
skills/wrap-up/ — session state capture
memory/ — 55+ memory files (MEMORY.md, sessions,
ledgers, project state, feedback, etc.)
settings/settings.json — user preferences (hooks, flags, no secrets)
Deliberately NOT backed up:
settings.local.json — contains operational secrets (HF_TOKEN,
SSH password in expect scripts); by naming
convention, *.local.* is not synced.
Needs separate review and probable rotation.
sessions/, history.jsonl, caches, telemetry — ephemeral
plugins/, marketplace skills and agents — reinstallable
The working copies at ~/.claude/skills/* and
~/.claude/projects/-Users-davidglidden/memory are symlinks into this
directory, so every write flows here automatically. install.sh
recreates the symlinks on a fresh machine.
FOLLOW-ON (flagged, not in this commit):
settings.local.json contains a HuggingFace token and an SSH password
as plaintext strings inside allowed Bash command patterns. These
should be rotated and moved to secure storage (keychain / pass /
env file outside the settings file).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.9 KiB
1.9 KiB
name, description, type
| name | description | type |
|---|---|---|
| Session 2026-04-08 evening | External Auditor naming, BMF rebuild + replay, resource monitor issue | project |
Session 2026-04-08 (evening)
What we did:
- Renamed all references from the reviewer's name to "the External Auditor" across 4 governance docs + PENDING.md + memory files
- Prepared reviewer package for the External Auditor (OP reading order + pre-read advisory)
- Pulled BetterMemories.io (Seb's c6689eb: Phase 2 fix, pairing persistence, recall ranking, entity BM25)
- Built clean — our stashed replay-coordinator changes fully superseded by Seb's version
- Restarted BMF via launchd (
com.capablemind.bmf) on new build - Diagnosed resource monitor feedback loop: CPU threshold fires on replay's own load, latency baseline freezes at startup — filed as #121
- Installed MemPalace (Python venv in
~/_Dev/mempalace/, data in.local-data/palace/) - Mined 191 thinking docs → 6,134 drawers across 11 rooms
- Wired MCP at user scope (
run-mcp.sh)
Thistleweld diagnostic chain: Entity persist eats 98% → CPU spinning despite sequential I/O → resource monitor pausing on its own load → frozen 5-sample latency baseline → filed #121
BMF state:
- Phase 2 replay running (~14 events/min, ~22K events total)
- Resource monitor feedback loop slowing replay (#121)
- Pairing mismatch with Seb's instance (non-urgent)
Open for morning:
- Memory palace technique study — David has sources (Yates, Carruthers, etc.) + personal practice with score memorization. Propose as Chamber source study or standalone inquiry.
- Wire MemPalace to ingest more directories (specs, chamber-library, session transcripts)
- Test MCP integration in fresh session
- Reviewer package ready for the External Auditor — David to send