How do I tell a stale RAG index apart from a truncated context window?

An answer from a stale index can pass faithfulness and groundedness because it accurately repeats an old chunk. Truncation is a context-presence failure: the right chunk was retrieved, then cut before the model saw it.

So compare what retrieval returned with what reached the model. If the needed chunk was never retrieved, the miss is in the index or the retriever, not proof that the context window cut it. If it was retrieved and then disappeared from the prompt, check context assembly and the window limit. If the model saw an old chunk and repeated it faithfully, compare that chunk with the current source and check when the index was last built.

Neither one shows up in the trace as an error. A tool returning stale data reads the same way, for the same reason: every span reports success.

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y