🔧 Auto-commit from sysupdate on 2026-05-29 09:43

2026-05-29 09:43:53 +02:00
parent ec6e414867
commit fffcf173c1
32 changed files with 2387 additions and 10 deletions
@@ -0,0 +1,17 @@
+---
+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
+---
+
+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.