memory-manager
Long-Term Agent Memory v2.1
Memory accelerates retrieval. It never replaces project files, and it never outranks them.
Layers
Classify every memory entry into exactly one layer, and attach scope and source:
AUTHOR_PROFILE → NOVEL_CANON → CURRENT_ARC → CURRENT_CHAPTER → CURRENT_SCENE → BRANCH_STATE → RESEARCH → TEMPORARY_WORKING_CONTEXT
Scope widens as durability increases. A scene-level observation that seems universally true is almost always wrong; promote it deliberately or let it expire.
What to persist
Record entries in memory/MEMORY_ENTRY.md.
Persist only meaningful durable state: established decisions, author preferences, resolved canon questions, active obligations, and long-running project constraints. Do not persist prose, restatements of what the Novel Bible already says unambiguously, or speculation about future work.
Prefer project files as the canonical source. Memory holds pointers and working knowledge that would be expensive to re-derive.