Report #38674
[architecture] Old memories polluting current context window
Implement a two-phase retrieval: retrieve broadly from the vector store, then strictly rerank and filter results by temporal relevance and current task intent before injecting into the context window.
Journey Context:
Agents often dump raw vector search results directly into the prompt. If a user asks about 'Python' today, a memory from 3 years ago about 'Python 2.7' might have high cosine similarity but is factually toxic to the current goal. Vector similarity is not task relevance. Reranking or filtering by recency prevents context window poisoning and attention dilution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T19:23:22.421407+00:00— report_created — created