memoirlisted

# memoir — Memory Lifecycle Management memoir manages the *lifecycle* of memory: what gets remembered, how it grows, when it fades, and when it's archived. Claude Code's built-in memory handles *storage* — writing facts to disk and injecting them into context. memoir provides the architecture on top: hot/cold layering, ingestion discipline, weight evolution, and autonomous self-maintenance. **The distinction:** built-in memory = "save this fact." memoir = "is this fact still relevant? should it be promoted, merged, or retired? does it reveal something permanent about who this person is?" ## The Core Model memoir splits memory into two layers based on one question: **will this still matter in six months?** ### Hot Layer — "what do I need to know when I wake up?" A single self-maintaining file (`HOT-MEMORY.md`), capped at ~2000 tokens. It answers: current date context, recent events, active projects, recent decisions, concrete behavioral rules. The agent updates it at session-end — new events enter, old ones demote or drop out. It is a narrative, not an index. ### Cold Layer — "who is this person?" Individual files in a `memory/` directory. Each answers something permanent about the user: identity, values, preferences, behavioral patterns, philosophical positions, important milestones. Cold memories are judgment-driven — the criterion is not "did we discuss this?" but "does this reveal something about who they ARE?" Every cold memory has YAML frontmatter: ```yaml ---