Busabase x Knowledge Base for MiMo CodeKnowledge Base for MiMo Code
MiMo Code deliberately persists project memory across sessions. That prevents rediscovery work, but it also means a checkpoint, note, or distilled workflow must not quietly become the team's authoritative record of a business decision.
MAP
Use persistent memory to recover context; use review to decide which conclusion survives as shared knowledge.
MiMo Code deliberately persists project memory across sessions. That prevents rediscovery work, but it also means a checkpoint, note, or distilled workflow must not quietly become the team's authoritative record of a business decision.
Project rules and architecture decisions
Structured session snapshots
Scratch and per-task work
Reviewed decision and evidence
01 · Knowledge Base for MiMo Code
MEMORY.md, checkpoint.md, notes.md, task progress
MiMo Code deliberately persists project memory across sessions. That prevents rediscovery work, but it also means a checkpoint, note, or distilled workflow must not quietly become the team's authoritative record of a business decision.
| Layer | Owns | Boundary |
|---|---|---|
| MEMORY.md | Project rules and architecture decisions | Repository guidance, not cross-system status |
| checkpoint.md | Structured session snapshots | Context recovery, not an acceptance record |
| notes and task progress | Scratch and per-task work | Useful execution evidence, often temporary |
| Busabase record | Reviewed decision and evidence | Accountable reuse beyond one repository |
02 · Knowledge Base for MiMo Code
SQLite FTS5 cross-session retrieval
Use persistent memory to recover context; use review to decide which conclusion survives as shared knowledge.
Automatic context reconstruction can make old assumptions feel current.
Knowledge extraction can improve memory, but must not bypass an owner for consequential facts.
A reusable Skill captures a procedure, not automatic approval of its output.
A judge-verified stop condition evaluates completion, not organizational acceptance.
03 · Knowledge Base for MiMo Code
subagents, workflows, Skills, MCP, /dream and /distill
Knowledge Base for MiMo Code: MEMORY.md, checkpoint.md, notes.md, task progress; SQLite FTS5 cross-session retrieval; subagents, workflows, Skills, MCP, /dream and /distill.
MEMORY.mdProject rules and architecture decisions. Repository guidance, not cross-system statuscheckpoint.mdStructured session snapshots. Context recovery, not an acceptance recordnotes and task progressScratch and per-task work. Useful execution evidence, often temporaryBusabase recordReviewed decision and evidence. Accountable reuse beyond one repositoryEVIDENCE
Knowledge Base for MiMo Code: inspect the execution boundary
CHECKPOINT: Automatic context reconstruction can make old assumptions feel current. DREAM: Knowledge extraction can improve memory, but must not bypass an owner for consequential facts. DISTILL: A reusable Skill captures a procedure, not automatic approval of its output. GOAL: A judge-verified stop condition evaluates completion, not organizational acceptance.
mimo-code_1MEMORY.md: Project rules and architecture decisions; Repository guidance, not cross-system statusmimo-code_2checkpoint.md: Structured session snapshots; Context recovery, not an acceptance recordmimo-code_3notes and task progress: Scratch and per-task work; Useful execution evidence, often temporarymimo-code_4Busabase record: Reviewed decision and evidence; Accountable reuse beyond one repository
ACCEPTANCE
Knowledge Base for MiMo Code: execution is not acceptance
Use persistent memory to recover context; use review to decide which conclusion survives as shared knowledge.
Automatic context reconstruction can make old assumptions feel current.
Knowledge extraction can improve memory, but must not bypass an owner for consequential facts.
A reusable Skill captures a procedure, not automatic approval of its output.
A judge-verified stop condition evaluates completion, not organizational acceptance.
PLACEMENT
Knowledge Base for MiMo Code: keep context with its owner
MEMORY.md owns Project rules and architecture decisions. checkpoint.md owns Structured session snapshots. notes and task progress owns Scratch and per-task work. Busabase record owns Reviewed decision and evidence.
| Layer | Owns | Boundary |
|---|---|---|
| MEMORY.md | Project rules and architecture decisions | Repository guidance, not cross-system status |
| checkpoint.md | Structured session snapshots | Context recovery, not an acceptance record |
| notes and task progress | Scratch and per-task work | Useful execution evidence, often temporary |
| Busabase record | Reviewed decision and evidence | Accountable reuse beyond one repository |
FRESHNESS
Knowledge Base for MiMo Code: record what can change
CHECKPOINT: Automatic context reconstruction can make old assumptions feel current. DREAM: Knowledge extraction can improve memory, but must not bypass an owner for consequential facts. DISTILL: A reusable Skill captures a procedure, not automatic approval of its output. GOAL: A judge-verified stop condition evaluates completion, not organizational acceptance.
source_versionhttps://github.com/XiaomiMiMo/MiMo-Coderuntime_factMEMORY.md, checkpoint.md, notes.md, task progress | SQLite FTS5 cross-session retrieval | subagents, workflows, Skills, MCP, /dream and /distillreview_ownerAccountable human reviewernext_reviewA stated recheck boundaryFAQ
Knowledge Base for MiMo Code: practical questions
Use persistent memory to recover context; use review to decide which conclusion survives as shared knowledge.
Does MEMORY.md replace a reviewed record?
No. It gives MiMo Code project context. A durable cross-team decision needs its own owner, sources, and review state.
Should every checkpoint be promoted?
No. Promote only a compact result that affects work outside the active task.
Can /dream write canonical business facts?
It can consolidate project memory. Verify those claims against their source system before proposing a canonical record.
Do subagents transfer acceptance authority?
No. They can return work in parallel; an accountable reviewer still accepts the reusable conclusion.
NEXT
Use persistent memory to recover context; use review to decide which conclusion survives as shared knowledge.
MiMo Code deliberately persists project memory across sessions. That prevents rediscovery work, but it also means a checkpoint, note, or distilled workflow must not quietly become the team's authoritative record of a business decision.