Memory

Status: next milestone. The design below is ratified in the seed document; the compiled MEMORY.md, candidates review and history search land after M2. This page describes the contract the memory system is being built to.

Two kinds of remembering

• Persistent memory is durable knowledge about you and your world: preferences, projects, environment, conventions, facts. It is stored as Markdown files owned by ka agent, written only through an explicit accept step, and injected into engines through Ka’s existing MEMORY.md convention.
• Episodic history is what happened and when: sessions, prompt cycles, final answers, outcomes, costs, errors. It is indexed by ka agent for search and links back to the authoritative strand for full detail.

History is not instruction: episodic content never becomes stable memory without an acceptance step.

The rules

• Plain Markdown, human-editable. Stable memory is files you can read, diff, and edit with any editor. There is no opaque store.
• Writes require acceptance. The engine’s remember tool only stages notes into an inbox; promotion into stable memory is an explicit review action. (The tool is disabled in worker engines: memory goes through ka agent, never around it.)
• Provenance. Every stable entry records where it came from.
• A budget. The compiled MEMORY.md injected into engines has a size budget; retrieval serves everything outside it, so memory cannot quietly crowd the context.

What exists today

The strict config, the state store and the audit chain (the substrate memory builds on) are in place. The user-facing pieces, /memory review and /history search, are the next milestone; see the roadmap.