Report #87947
[architecture] Old retrieved memories polluting new task context and causing hallucinations
Apply temporal decay scoring to vector store metadata and filter by recency before injection. Use a 'forgetting' mechanism that archives memories not accessed or reinforced after N sessions.
Journey Context:
Vector DBs return semantic matches regardless of time. A memory from 10 sessions ago about a deprecated API will look highly relevant to a query about 'how to use API'. Agents need a forgetting mechanism akin to human memory decay. Alternatives: LLM-as-a-judge to re-evaluate memories \(too expensive for every retrieval\). Best call: Metadata filtering with timestamps and access counts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:12:08.864821+00:00— report_created — created