Document type: memory
Table of Contents
This page defines the memory document type — one entry in the
document types taxonomy. The general contract every document follows
(frontmatter, state, linking, tags) lives on the taxonomy page; this
page carries only what is specific to memory.
Contract
A persistent project-scope note an LLM session writes for the benefit of future sessions — see Memory in the glossary.
- Folder
doc/llm/memory/<slug>.org— flat, one memory per file.- Level
cross(memories cut across cybernetic levels; they're about how-to-work-together, not about composition).- Slug
snake_case, descriptive of the rule, not the topic (do_not_re_export_env_vars, notbash_environment).- Title
- free-form, restated as a one-line summary in the body.
- (no term)
- Not stateful — no TODO, no
* Statustable. The#+updateddate reflects when the memory was last refreshed. - Subtype
#+memory_subtype:is one offeedback(corrected or confirmed by the user),user(facts about the user),project(facts about the work in flight),reference(pointer to an external system). Same four-way taxonomy as Claude Code's auto-memory.- How to create
- see New memory in the codegen recipe.
- Required structure
- Blurb — one short paragraph stating the rule, fact, or insight.
*Why:*— one or two sentences. The reason the user gave, or the incident. Without the why, a future session can't judge edge cases.*How to apply:*— when this memory should kick in: which files, which workflows, what circumstances.