Report #79814
[architecture] Retrieving semantically similar but temporally obsolete memories that contradict current facts
Implement time-weighted retrieval scoring \(e.g., exponential decay\) combined with semantic similarity, and explicitly tag memories with an expiration or invalidation context.
Journey Context:
Pure cosine similarity ignores time. A memory from 2 years ago about a user's address might be semantically identical to a query about their address, but factually wrong. Combining semantic score and a recency score via Reciprocal Rank Fusion solves this. Alternatively, write-time invalidation \(updating a memory marks the old one as is\_current: false\) is more reliable but harder to implement perfectly than read-time decay.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T16:33:51.433037+00:00— report_created — created