1.4 KiB
1.4 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| mempalace-is-unaffiliated-stopgap | 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. |
|
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.