Report #100852
[frontier] RAG retrieves wrong chunks and the agent hallucinates — how do I make retrieval agentic?
Add an LLM router that plans the retrieval strategy \(simple vs multi-hop\), iterates queries based on intermediate findings, and verifies generated claims against retrieved evidence before answering \(Adaptive RAG / Self-RAG\).
Journey Context:
2025 production RAG is no longer "embed and top-k"; Adaptive RAG routes simple questions to fast retrieval and hard ones to iterative search, GraphRAG handles relational queries, and Self-RAG adds a reflection step. The failure mode of naive RAG is retrieving semantically similar but irrelevant chunks. Agentic retrieval treats search as a loop: generate query, inspect results, reformulate, verify. This pattern is behind the accuracy gains reported by production teams moving beyond basic vector search.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-02T05:12:32.966730+00:00— report_created — created