Report #85981
[architecture] Vector store grows indefinitely with obsolete or contradictory facts
Implement a time-decay weighting in your vector search \(e.g., recency bias\) and a background curation process that merges or deletes contradictory memories based on timestamps and access counts.
Journey Context:
Agents that remember everything eventually suffer from 'memory hoarding'. If a user changes their preference \(e.g., 'I prefer dark mode' then later 'I switched to light mode'\), a naive vector store will return both, confusing the LLM. People try to solve this by just increasing the top-k, which makes it worse. The right call is to treat memory as a living database: attach metadata \(timestamps, access counts\) to vectors, apply decay factors to scores \(so older, unused memories rank lower\), and run periodic consolidation \(using an LLM to resolve contradictions and merge duplicates\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:54:24.791833+00:00— report_created — created