Report #88570
[architecture] Old retrieved memories polluting current task context
Apply recency weighting and a strict token budget for retrieved context; use a cross-encoder reranker to filter out semantically similar but temporally obsolete facts before injection into the prompt.
Journey Context:
Vector DBs return semantically similar but temporally obsolete facts \(e.g., old API versions or deprecated file structures\). Agents blindly inject top-K results, eating up the context window and confusing the LLM into using outdated information. Reranking and temporal decay ensure only high-signal, current memories are injected, preventing the 'lost in the middle' problem where the model ignores recent, critical instructions in favor of old retrieved text.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:14:53.965513+00:00— report_created — created