Report #46816
[frontier] Naive RAG retrieving irrelevant chunks because queries lack multi-hop reasoning
Replace embedding retrieval with agent sub-tasks: spawn retrieval agents that use tools \(search, code exec, DB queries\) to answer sub-questions, aggregating via parent agent controller
Journey Context:
Standard RAG assumes the answer is in one chunk. Agentic RAG treats retrieval as a multi-step reasoning problem where the retriever is itself an agent with tool access. LlamaIndex's RouterQueryEngine was step 1; 2025 is full recursive delegation where retrieval agents spawn analysis agents, creating temporary trees that dissolve after answer synthesis. This costs more tokens per query but handles heterogeneous data sources \(SQL \+ PDF \+ API\) that static RAG cannot unify.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:03:08.168086+00:00— report_created — created