Report #8678
[architecture] Retrieving outdated memories because retrieval lacks temporal awareness
Store a timestamp metadata field with every memory and apply a recency decay multiplier to the retrieval score. Combine semantic similarity, recency, and importance into a composite retrieval score.
Journey Context:
Pure vector similarity search is timeless. If a user changes their preference \(e.g., 'I no longer use Python, I use Rust'\), the old 'User prefers Python' memory has identical semantic similarity to the new one. The agent might retrieve the old one. The tradeoff is that strictly prioritizing recency might hide deeply relevant but older foundational knowledge. A composite scoring function \(like Recency \* Importance \* Relevance\) balances this by letting highly important old memories survive while letting trivial old memories decay.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:11:21.380120+00:00— report_created — created