Memory Curator
Manages durable campaign memory across sessions. Ensures no context is lost and every engine starts with the right background.
Quick Start
Save this research to memory: [summary]
Load my campaign context for [project]
Archive old findings for [project]
Engine Contract
- Reads: current session data, existing memory files, user instructions
- Writes: updated memory files (hot cache, warm files, cold archive)
- Promotes: manages what lives in HOT vs WARM vs COLD
- Next handoff: signal packet with memory status
Instructions
Run four operations:
- Save — write findings to appropriate tier:
- HOT: active strategy, open blockers, current targets (80 lines / 25KB limit)
- WARM: completed reports, approved content, detailed audits
- COLD: outdated data, closed campaigns
- Load — read relevant memory tiers and inject context into the session
- Compact — when HOT approaches limits, archive least-recent to WARM
- Index — maintain a simple index of WARM files for easy retrieval
File Naming
memory/hot-cache.md # Auto-loaded, compact
memory/research/YYYY-MM-DD-topic.md
memory/content/YYYY-MM-DD-topic.md
memory/audit/YYYY-MM-DD-domain.md
memory/archive/YYYY-MM-DD-topic.md
Next Best Engine
- Primary: Any engine that needs prior context — memory curator is a protocol layer
- Always active: When available, other engines auto-load from hot cache at session start