Report #55236
[architecture] Stale memories overriding current facts \(no temporal decay\)
Attach a timestamp and access count to every memory. Apply a time-decay multiplier to the retrieval score \(e.g., exponential decay\) and boost frequently accessed memories, similar to a relevance-weighted LFU cache.
Journey Context:
Vector databases treat all documents as equally timeless. An agent that remembers a user's project directory from a year ago will hallucinate file paths that no longer exist. Pure recency \(only keeping last N days\) destroys long-term rare knowledge. A decay function allows recent facts to naturally supersede old ones, while an access-count boost ensures critical, timeless facts \(like core user preferences\) resist decay.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:12:21.933177+00:00— report_created — created