Report #43098
[architecture] Agent retrieving semantically similar but temporally obsolete information
Store metadata timestamps alongside vectors and use hybrid search \(vector similarity \+ recency decay scoring\) or strict metadata filtering.
Journey Context:
A query like 'How do I configure the API?' might retrieve a 2-year-old answer that is completely wrong for the current version. Pure semantic similarity ignores time. Adding a recency bias \(e.g., exponential decay on the retrieval score based on timestamp\) or strict date-range filters ensures the agent uses the right version of the truth.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T02:48:47.812021+00:00— report_created — created