Concepts

This section explains how zero-memory represents knowledge and why it is built the way it is.

• Memory model — memories, kinds, entities, links, and the MCP tools that operate on them.
• Canonical language — why stored content is canonical English, and how other languages are handled on write, read, and in the dashboard.
• Scopes and isolation — personal, project, and team scopes, explicit membership, project-isolated reads, how a session attaches to its project (and why an unattached write is refused), and the verified portable layer.
• Agent principals — how non-human writers are identified and what that identity enables across memories, activity, and metrics.
• Identity — prefixed domain identifiers, branded id contracts, the system-of-record rule, and how a project is identified.
• Provenance — who wrote a memory, how that ranks it, and which client it came from.
• Supersede and versioning — how facts are updated without creating duplicates, and how version history forms behind a current fact.
• Open loops — tasks and open questions that persist in briefings until closed.