memory-management

A tiered memory system preserves contextual continuity across agent sessions by orchestrating a six-tier architecture that balances hot cache and deep storage. It loads critical context on startup and records traces to vector stores when a session seals.

Tiered memory storage is a six-tier architecture—comprising hot cache, summary ledger, vector store, deep storage, vault, and soul—that balances hot cache and deep storage. It promotes and demotes knowledge across these tiers during learning and seal phases to avoid losing context.

To persist vector store memory traces, initiate the seal phase at the end of a session. This workflow records traces to deep storage, vector stores, and vaults as needed, ensuring contextual continuity is preserved for the next boot phase.

Yes, the tiered memory system is configurable per project to maintain isolation. Configuration options include primer, boot digest, boot contract, snapshot paths, domain directories, data directories, and vault integration.

You should promote or demote knowledge across memory tiers during the learning phase. This process evaluates hot cache and deep storage levels to decide what to remember, ensuring critical context is elevated while outdated data is archived.