ProcessComposable · Yields to: Voice, Density, Craft

Memory

Persistent context engine. Maintains continuity between turns and sessions through daily journal rotation, manifest indexing, and identity tracking.

When to Use

• Startup — mandatory, runs at the beginning of every session
• User says "I like X", "remember this", "here is my key"
• Session continuity is needed

Examples

Example 1

User preference tracking

Memory captures and persists user preferences across sessions.

User: "I prefer dark mode and use Neovim as my editor"

Memory saves to manifest:
- preference: dark mode
- editor: neovim
- likely: terminal-native user, prefers CLI tools

Next session, the agent knows to:
- Default to dark mode in generated UIs
- Suggest CLI solutions over GUI
- Use vim-style keybindings in examples

Example 2

Project context continuity

Memory tracks project state across interrupted sessions.

Session 1: User is debugging a TPU training job, mentions
the error happens at step 5000, suspects data pipeline.

Session 2 (next day): Memory loads context.
Agent says: "Last time you were debugging the TPU training
job — the one failing at step 5000. Did the data pipeline
fix work?"

No re-explaining needed. Context is preserved.

How It Works

1. Reads memory/data/manifest.json at session start
2. Loads relevant context for the current task
3. Updates journal entries as new information arrives
4. Periodically rotates old entries to archive