Report #82709
[architecture] Storing all memories at same granularity in a flat collection
Implement tiered memory: short-term working buffer \(current conversation\), mid-term episodic store \(summarized session insights\), and long-term semantic store \(core facts, preferences, learned patterns\). Each tier has different retention policies, retrieval mechanisms, and consolidation triggers.
Journey Context:
A flat memory store treats a fleeting observation identically to a core fact \('user prefers Python over JavaScript'\). This creates retrieval noise and storage waste. Human cognition separates working, episodic, and semantic memory for good reason—each has different access patterns, retention, and granularity. The MemGPT architecture explicitly models main context \(working\), recall memory \(conversation history\), and archival memory \(long-term knowledge\). Without tiers, retrieval returns a mix of trivial and critical memories at wrong granularity, and you cannot apply different lifecycle policies to different memory types.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:25:15.656732+00:00— report_created — created