Report #37027
[architecture] Long-term memory only grows, causing stale facts to pollute retrieval and contradict new information
Implement memory decay via metadata timestamps and importance scores, and use a background curation process to update or delete contradicted memories.
Journey Context:
Vector databases are append-only by default. Without curation, an agent will eventually retrieve a user's outdated preference \(e.g., 'I prefer Python 2'\) over their current one. Unlike a relational database that can simply UPDATE a row, vector embeddings are immutable. The fix is to attach expiration/decay metadata and run a consolidation loop: when a new fact contradicts an old one, delete or update the old embedding. This prevents context window pollution from stale data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T16:37:34.849984+00:00— report_created — created