Skip to content
MemMini

Quickstart — pick your level

Same files, four depths. Start at the rung that’s you; you can climb later without starting over.

This is the install-depth knob — how permanently MemMini lives with you. You don’t need any of it to get value (ask for an outcome first); pick a rung when you want it to stick.

Level 1 — I don’t code

Section titled “Level 1 — I don’t code”

You live in AI chat.

  1. Open context/who.md on GitHub and copy it.
  2. Paste it into your AI chat at the start of a conversation.
  3. Edit a line to match you (see Write your first rule).

Every reply now follows your rules and sounds like you — no syntax, ever.

Level up → tired of re-pasting? The next rung makes it permanent: fork it once.

Level 2 — I vibe-code

Section titled “Level 2 — I vibe-code”

You build with AI tools.

Terminal window
# Fork on GitHub, then:
git clone https://github.com/<you>/MemMini && cd MemMini
# edit context/who.md + context/how.md

Your facts and your style now travel with every AI tool you build with, and the repo captures what changed after each session.

Level up → want your agents coordinating through the repo, not through you? Next rung, same fork.

Level 3 — I code

Section titled “Level 3 — I code”

You have a real workflow.

You’re still on the fork from Level 2 — now point every agent at it. They read and write the same repo, so they hand work to each other through git — coordination with no orchestration server to run. Be the boss, not the bus. (How work flows here walks one handoff start to finish.)

When a submodule helps: if your mind lives inside a bigger project of your own, or you send fixes back upstream, mount it as a .mind folder instead — git submodule add https://github.com/aaron-earle/MemMini .mind — same files, kept as a separate piece. Otherwise stay on your fork.

Level up → running more than one agent at once? Compile overlays per surface.

Level 4 — I orchestrate agents

Section titled “Level 4 — I orchestrate agents”

Fleets, frameworks, multi-vendor.

Terminal window
./scripts/compile-context.sh --overlay ./my-org --platform my-stack
# → CONTEXT.md (inject) + ENFORCEMENT.md (route) per surface

You get routed enforcement, cross-vendor agent coordination, and self-distilling memory — agents coordinating through one repo you own, you out of the middle.

The compile step layers content in order: framework defaults → your --overlay → an optional --platform layer. Same-name files replace; extra files append; your behavioral who.md is never pulled from a platform layer. Full model and flags: Repo layout.

Next

Section titled “Next”