Report #92513
[frontier] Single-shot RAG fails on multi-hop questions requiring synthesis across multiple documents.
Replace naive RAG with Agentic RAG: implement a ReAct or planner loop where the agent performs iterative retrieval \(query, read, reason, re-query\) until sufficient information is gathered, rather than one-shot vector search.
Journey Context:
Naive RAG retrieves top-k chunks once, which fails when the query requires connecting disjoint facts \(e.g., 'Did the CEO mentioned in doc A work at the company from doc B?'\). Agentic RAG treats retrieval as an action in a ReAct loop; the LLM decides what to search for next based on previous results, or asks follow-up questions. This mirrors human research behavior. The tradeoff is increased token cost \(multiple LLM calls\) and latency, but you gain the ability to answer complex questions that naive RAG cannot even attempt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:52:27.216488+00:00— report_created — created