Why did my RAG answer miss the exception to the rule?

Somewhere in your chunking step, the rule and its exception landed in two different chunks, and only one of them came back. A chunker that splits on paragraph or token count doesn’t know a sentence three lines down changes everything above it, so it cuts wherever the boundary falls, not where the meaning does. The retriever then scores each chunk against your question independently. The chunk with the general rule matches well; the chunk with the narrow exception, if it doesn’t share the query’s vocabulary, may not surface at all.

The model isn’t hallucinating here. It’s being faithful to exactly the context it was handed, which is what makes this failure invisible to any check that only grades the answer against its own context. One writeup of a compliance RAG pipeline traced this exact failure to a chunk that ended mid-sentence, right before the exception clause. The fix lives in chunking and retrieval, not in the model.

sources

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