Report #14848
[architecture] Agent retrieves a fact from the past and applies it to the present without realizing it is outdated
Attach strict metadata \(timestamps, version numbers, session IDs\) to memory chunks. During retrieval, filter or heavily weight by recency, and instruct the LLM to check the temporal validity of retrieved context before acting.
Journey Context:
Vector embeddings are timeless. 'The server IP is 192.168.1.1' has no concept of when it was true. Without metadata filtering, the agent will confidently use outdated info. Embedding similarity alone cannot distinguish between a fact from yesterday and a fact from a year ago. The tradeoff is the engineering overhead of metadata extraction and filtering pipelines, but it is strictly required to prevent time-travel hallucinations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:38:20.880102+00:00— report_created — created