Skip to content
MemMini

Framework, mind, surfaces

MemMini has four layers. Keeping them straight is the whole mental model — it tells you what’s yours, what’s shared, and how “the version of you” actually reaches a tool.

The four layers

Section titled “The four layers”

MemMini — the framework. The language and schema: how context/ is written, how the wiki/ graph links, the distill loop, the contracts. Open-source, nobody’s mind. You consume it; you don’t edit it to be you.

Your mind — your instantiation of the framework. Fork MemMini and the result is yours: your identity, your knowledge, your coordination, in one portable repo. (The maintainer’s own mind is called agent-mind; yours is whatever you name your fork.) A mind is host-independent — it belongs to no single app.

Surfaces — where your mind runs. Claude Code, Codex, a chat app, an agent harness. Each is a host with different capabilities — some run code, some schedule, some can’t. A surface hosts a mind; it doesn’t consume the framework.

The agent-bootloader — the loader between them. A mind doesn’t reach a surface by magic. The bootloader brings it up: it probes what the surface can do and translates your six intentions onto that surface’s real buttons, with a degrade rule for anything missing. It belongs to neither side — it’s the adapter between mind and host. Put your mind on your tools is its easy button.

Why it matters

Section titled “Why it matters”

The split is what makes “one you, everywhere” both real and safe:

  • The framework improves without touching who you are — pull updates; your mind stays yours.
  • Your mind is portable — the same fork runs on every surface, so you never re-explain yourself per tool.
  • Surfaces are swappable — a new tool is just another host to bootload; nothing about your mind changes.

Go deeper

Section titled “Go deeper”