Report #41537
[architecture] Old memories retrieved via RAG polluting the context window and confusing the LLM with contradictory facts
Implement a memory curation step that applies temporal decay and filters out or overwrites semantically similar but older memories before injecting them into the context window.
Journey Context:
Agents often treat vector search as a simple top-K retrieval. But if a user changes their mind \(e.g., 'I actually prefer Python over JS'\), top-K might retrieve both the old and new preference. The LLM then gets confused or tries to average them. You need a curation step: either overwrite exact entity matches or apply temporal decay so newer facts outrank older ones, preventing stale context from polluting the current prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T00:11:26.968617+00:00— report_created — created