memory-management

1# Memory Management
2 
3Manages the project's authorized working memory. HOT/WARM/COLD notes improve retrieval; they are not a second truth system. The seven registry event streams remain canonical, their JSON projections are rebuildable views, and only registry owners may accept or mutate canonical facts.
4 
5## Quick Start
6 
7```text
8Initialize private runtime memory from the repository templates.
9Show current priorities and their source records.
10Consolidate duplicate notes without changing registry truth.
11Archive WARM files not updated in 90 days.
12Purge subject-7f42 from project memory under this confirmed erasure request.
13```
14 
15## Skill Contract
16 
17**Reads:** authorized runtime memory, registry projections/events, approved decisions, and [state-model.md](../../references/state-model.md). **Writes:** HOT/WARM/COLD notes, archives, indexes, and authorized tombstone/erase events; it never accepts registry proposals or writes canonical facts on behalf of an owner. **Done when:** the requested operation is complete, writes have explicit authorization, affected paths/events are reported, HOT is within 80 lines and 25 KB, and registry verification still passes.
18 
19Operational `memory/**` is Git-ignored by default. Initialize from `memory/templates/`; never commit runtime data, event streams, projections, audits, exports, or subject records unless the user deliberately creates a separate protected data-governance process.
20 
21### Authority Order
22 
23When sources conflict, use this order:
24…