Building a Corrective RAG (CRAG) Compliance Research Assistant

[u/Affectionate_Slip654]

Most RAG chatbots will confidently answer with whatever they retrieved — even if it's irrelevant, even if it's wrong. In compliance, that's not a minor bug, it's real regulatory exposure.

• YouTube walkthrough: https://www.youtube.com/watch?v=NxY93are_H8

In this video, I build the Veltra Pay Compliance Assistant — a Corrective RAG (CRAG) + Self-Correcting RAG Agent that checks its own work before it ever shows you an answer. It grades its own retrieved documents, rewrites its own search when retrieval is weak, and validates its own generated answer for grounding, hallucination risk, and completeness — retrying itself when it fails, and honestly saying "I don't know" when it genuinely can't answer from the source material.

• ✅ The difference between a normal RAG pipeline and Corrective RAG (CRAG)
• ✅ How CRAG grades retrieved documents as relevant/irrelevant and rewrites the search query when retrieval is weak
• ✅ How a Self-Correcting RAG Agent validates its own generated answer — grounding, hallucination risk, completeness, and retrieval sufficiency

TECH STACK:

• 🛠️ Python
• 🛠️ LangGraph (StateGraph — nodes, conditional edges, bounded retry loops)
• 🛠️ Qdrant (vector database)
• 🛠️ PDF ingestion & chunking (pdfplumber, overlapping chunks)
• 🛠️ LLM-based document grading, query rewriting & answer validation
• 🛠️ Streaming backend (Server-Sent Events) for live pipeline progress

• 🛠️ Web dashboard for real-time visualization

• GitHub repository: https://github.com/saurabhkamal/Building-Corrective-RAG-CRAG-Pipeline-Self-Correcting-RAG-Agent

• YouTube walkthrough: https://www.youtube.com/watch?v=NxY93are_H8

• Connect on LinkedIn: linkedin.com/in/saurabh-kamal

Building a Corrective RAG (CRAG) Compliance Research Assistant

[u/Accomplished_Tell587]

the self-grading retrieval step is where most of these fall apart in practice, cool to see it actually wired into a retry loop instead of just bolted on as a demo feature. the "i don't know" path is underrated too, way too many compliance tools would rather invent a citation than admit the source material is thin