Report #69467
[architecture] Old memories retrieved via RAG pollute the context window and cause the agent to hallucinate or apply outdated state to new tasks
Implement a strict temporal decay and state-invalidation mechanism. Tag memories with entity versioning \(e.g., user\_preferences\_v2 invalidates v1\) rather than just appending new vectors, and apply TTLs to transient state.
Journey Context:
Naive RAG just appends retrieved text to the prompt. If a user changes their preference, both old and new are retrieved, confusing the LLM. Vector similarity does not respect time or state mutations. State-invalidation via entity overwriting or TTLs prevents stale data from entering the context, treating memory more like a mutable database than an append-only log.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:05:01.687110+00:00— report_created — created