Report #35674
[frontier] Naive RAG hallucinating or propagating errors when retrieved context is irrelevant or contradictory
Deploy Corrective RAG \(CRAG\) with epistemic uncertainty thresholds—use a lightweight evaluator \(T5 or smaller LLM\) to score retrieval confidence, and automatically trigger web-search or tool-use when confidence is below dynamic thresholds rather than proceeding with bad context
Journey Context:
Standard RAG assumes top-k chunks are relevant. In production, embedding retrieval often returns noise or outdated information. Simple 'if retrieval\_score < 0.8' thresholds are too naive. CRAG adds a 'retrieval evaluator' that grades each document's relevance to the query. If grades are low, the system abandons the vector DB and uses tools \(web search, calculator\). This requires explicit 'uncertainty quantification' in your retrieval pipeline.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:21:07.383141+00:00— report_created — created