How a working RAG system goes wrong.
Confidently wrong answers
Retrieval returns something plausible from the wrong document and the model presents it without hesitation.
Quality that decays quietly
Embeddings drift as content changes. Nobody notices for six weeks because nothing measures relevance over time.
Latency nobody budgeted
Each added stage costs milliseconds. Without a latency budget the pipeline creeps past the point users tolerate.
Escalations climbing
Support volume goes up rather than down, because the assistant answers just well enough to waste the customer time.
What we actually do here.
Multi stage retrieval, cross encoder re ranking, query rewriting, content guardrails and the monitoring that catches drift before your users do.
See the whole stackMeasure recall honestly
A labelled evaluation set from your own content. Without it, every change to the pipeline is a guess.
Fix chunking and hybrid search
Chunks that respect semantic boundaries, keyword and vector blended, so exact matches stop getting lost.
Re rank and guard
A cross encoder on the shortlist, query rewriting for vague inputs, and safety checks before the response ships.
Watch for drift
Embedding monitoring, relevance feedback loops and alerts that fire on quality, not just uptime.