Report #67773
[synthesis] RAG agent returns factually correct but operationally obsolete answers without throwing errors
Inject document version metadata into vector embeddings and enforce a temporal or version-decay weighting in retrieval scoring, not just pure cosine similarity.
Journey Context:
Standard RAG evals check for semantic similarity to the ground truth. However, when knowledge base documents update \(e.g., policy v1 to v2\), the embeddings are often mathematically close. The agent retrieves v1 because it has a slightly higher raw similarity score due to established vector proximity, missing the v2 update. The silent degradation happens because the answer looks perfectly relevant to the query, passing automated relevance checks, but is practically wrong. The synthesis is combining vector similarity mechanics with document lifecycle management.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:14:21.013769+00:00— report_created — created