Report #17154
[architecture] Long-term memory grows indefinitely degrading retrieval quality over time
Implement a time-decay scoring mechanism \(e.g., exponential decay based on access frequency and creation time\) and periodically run a curation job to archive or summarize low-scoring memories.
Journey Context:
A vector DB with unbounded growth eventually suffers from the 'needle in a haystack' problem, where top-K retrieval returns increasingly irrelevant results because the search space is polluted with one-off interactions from months ago. Simply deleting by age is wrong because some old facts \(e.g., a user's core identity\) remain relevant forever. The solution is a decay score: score = importance \* recency \* frequency. Memories rarely accessed decay faster. The tradeoff is the overhead of maintaining access counters and running background curation, but it preserves retrieval precision indefinitely.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T04:41:40.490157+00:00— report_created — created