grim:mem:dream-sequence · git:20260827.f7d7117 · 2026-08-27 · sha256 f38291bd4fbc5561
grim:mem:dream-sequence git:20260827.f7d7117A
Immutable. This exact content is served forever at /api/v1/blob/f38291bd4fbc5561.
--- name: grim:mem:dream-sequence description: "Dream Memory Sequence: Run a periodic memory-consolidation review. Synthesize recent work and chat history, propose durable memory candidates, flag stale or duplicate memory for cleanup, and surface missing-context questions. Never edits memory without user confirmation." --- # Dream Memory Sequence ## Purpose Consolidate and improve the memory system, the way sleep consolidates a day's experiences. Run this weekly, or after an intense stretch of work. Memory flows in one direction: `memory/MEMORY.md` is the fast-capture surface where corrections and preferences land mid-session, and the dream sequence is the consolidation pass. Durable items that have proven themselves get promoted out of memory into the right `docs/` file (or `AGENTS.md`, per `grim:dev:autodocs`), then pruned from memory. Memory stays small; docs accumulate the distilled knowledge. ## Inputs Review before summarizing: - `memory/MEMORY.md` (and the project's memory system docs, if any) - `docs/README.md` and any recently changed docs - Recent chat or session history from the last 7 to 14 days, when the harness makes it available ## Report Return a report with: - A synthesis of the recent period, highlighting the most important things to remember - Durable memory candidates, to be added to memory - Promotion candidates: memory entries that have matured into doc material, with the target `docs/` file for each (prune from memory once promoted) - Stale, duplicate, or low-signal memory cleanup suggestions - The top 3 missing-context questions that would help the system better understand the user's life, goals, and projects - Suggested next steps ## Rules - Do not silently edit any docs, skills, memory files, commits, or external systems until the user confirms. - Distill, don't transcribe: one bullet per durable fact. - Prefer correcting an existing memory entry over adding a near-duplicate.