Memory Bank
The foundational Dotabase holding episodic memories — durable observations, decisions, rationale, and failures worth keeping across sessions. Rows are MEM-N.
Memory Bank is not a passive log. Its rows decay, are reinforced when they prove useful, and graduate into DOTs when they stabilize — the reinforcement schedule runs on FSRS (the spaced-repetition algorithm), with per-memory-type configuration. Agents grade a retrieved memory after use: grade 3 if it helped, grade 1 if it misled, with grade 4 reserved for John's own confirmation.
The recall discipline is bounded, not blanket: an agent runs a Memory Bank recall before non-trivial work on an existing surface, and again after two failed attempts at the same obstacle.
Usage examples
- "Episodic memories that decay, reinforce, and graduate into ." (the 's own description)
- "After two failed attempts at the same obstacle, run one bounded memory recall before a third — cite
MEM-Nor state none found." - "
dots memory reinforce MEM-464 --grade 3— that one saved us the flat-props failure again."
Source
AGENT-GOVERNANCE.md § Architecture (foundational Dotabases) and § Guardrails (the recall and grading rules); identity and FSRS model at SPEC-168 (DS_Memory-Bank); consumer contract at SPEC-385.
Memory Bank · This page in the graph
- mentionstoDots
- mentionstoDotabase
- mentionsfromMCP Tools
- mentionsfromQuickstart
- mentionsfromFoundational And Internal Dotabases
- mentionsfromWhat Is Dots?
- mentionsfromConversation Insights Dashboard
- mentionsfromQuickstart: Self-hosting Dots
- mentionsfromAutomate Work With Chat Automations
- mentionsfromChat Overview
- mentionsfromGive Chat The Right Context
- mentionsfromCLI Reference
- mentionsfromDotabase