Files
dotfiles/claude/memory/mempalace-is-unaffiliated-stopgap.md
T
David F GliddenandClaude Opus 4.8 3f9a89b00c chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)
Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized
live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds
long YAML description lines, strips final newlines. Bodies untouched —
verified via full diff classification. From this commit forward, any diff in
claude/memory shows only what Basic Memory or the session writes.

Trial design: MemPalace untouched as incumbent; git status check on this dir
at every wrap; end-of-day evaluation (recall quality, sync robustness,
rebuild-from-files, malformed-file behavior).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-06 09:52:17 +02:00

20 lines
1.5 KiB
Markdown

---
name: mempalace-is-unaffiliated-stopgap
description: MemPalace is a third-party tool with NO affiliation to the steward or
Seb. They build BMF/CapableMind (which is hoped to replace MemPalace one day). Do
not conflate the two; MemPalace PRs await its own maintainers, not Seb.
metadata:
node_type: memory
type: project
originSessionId: 96ac9e09-7d3d-4ce3-a9cb-5234078a2a4e
permalink: claude-memory/mempalace-is-unaffiliated-stopgap
---
MemPalace is a **third-party, unaffiliated** project. The steward uses it as his memory substrate *while BMF (CapableMind L1) is in development*, and hopes BMF will one day **replace** it. Neither the steward nor Seb has any affiliation with MemPalace.
Concretely:
- Upstream MemPalace issues/PRs (the hallways #1619/#1620, the L1-recency #1629/#1630) await the **MemPalace maintainers** — *not* Seb. Never describe them as "awaiting Seb" or as CapableMind work.
- Do **not** conflate MemPalace's architecture or roadmap with BMF/CapableMind. They are separate codebases by separate people.
- Lessons drawn from MemPalace (e.g. [[feedback-rank-on-fields-you-actually-write]]) matter *because* they inform our own tool-building (BMF/CapableMind/studium-engine), not because the codebases are related.
**Why this is worth holding:** the tools are deeply intertwined in the steward's daily use (MemPalace *is* the live memory while BMF matures), which invites the conflation — and I have made it more than once. The steward has had to correct it "again," so this is the durable correction.