Field Note — one real failure, the wrong diagnosis, the actual cause, the fix.
The assistant did not hallucinate. It told the truth — about a world that no longer existed. That distinction is the difference between a model problem and a pipeline problem, and almost everyone reaches for the wrong one first.
The symptom
An internal RAG assistant answered a policy question with total confidence and complete wrongness — it quoted a refund window that had been changed six weeks earlier. The wording was precise, sourced, and obsolete. Users reported it as “the AI making things up.”
The wrong diagnosis
“The model hallucinated — add a stronger system prompt, turn down the temperature.” None of that would have helped, because the model did not invent anything. It faithfully summarised a document that was sitting right there in the retrieval results. The failure happened before the model ever saw the query.
The actual cause
The vector index was stale. The source policy had been updated, but re-embedding ran on a weekly batch, and the old chunks still carried the highest similarity score for that question. Worse, the previous version of the document had been edited in place rather than tombstoned, so there was no signal that the retrieved chunk was superseded. The model did exactly its job: it grounded its answer in the most relevant document it was handed. The document was simply six weeks out of date. RAG does not protect you from stale truth — it launders it into a confident sentence.
The fix
Treat index freshness as a service level objective, not a cron job nobody watches. Re-embed on source change, incrementally, so an edit propagates in minutes rather than at the weekly boundary. Carry a last-updated timestamp on every chunk and let ranking prefer recency when relevance scores are close. And honour deletes: when a source is removed or superseded, its vectors must leave the index, not linger as a high-scoring ghost.
# A retrieved chunk is not just "relevant" - it has an age.
for chunk in results:
if chunk.source_updated_at > chunk.embedded_at:
stale.append(chunk) # the index is behind the source of truth
# Alert when stale/total crosses the freshness SLO.
# Re-embed on source change; tombstone on delete; recency breaks ties.
The reframe
RAG does not hallucinate here. It repeats, faithfully, whatever your index believes to be true. The model was not wrong about the facts — it was right about a world that had already moved on. Retrieval quality is not a model property. It is a freshness discipline, and it decays the moment you stop maintaining it.
Leave a Reply