Dream Consolidation Cycle
Run a deeper, slower reflection pass distinct from per-tick reflection — reading hours of recent thoughts, promoting themes, releasing affective residue, and clearing working memory — so the agent does not accumulate residue indefinitely.
Problem
Per-tick reflection is too shallow to notice that a theme has been recurring all afternoon, and the weekly insight pass is too coarse to release the affective residue from yesterday's tense exchange before today begins. Without an intermediate sleep-like pass that runs every few hours, the agent keeps ruminating on stale items, its affect scalars never get a chance to decay back toward baseline between sessions, and working memory stays cluttered with threads it should have either consolidated or let go.
Solution
On a slow timer (every few hours, or when an affect scalar crosses a threshold), pause normal ticking. Load the last few hours of thoughts and affect history. Run a stronger model with a dream-pass prompt that distils themes into journal entries, applies decay to all affect scalars, optionally clears workspace focus, and appends the dream summary to a dedicated dream-journal surface. Persistent learning (rules, charter, insights) is not edited here; the dream pass produces proposals that a subsequent reflection pass can ratify.
When to use
- The agent runs continuously enough to accumulate hours of recent thoughts that need consolidation.
- Affective residue or working-memory clutter measurably degrades reasoning over time.
- There is a separate dream-journal write surface distinct from charter/rules/insights.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.