Report #59842
[synthesis] Why single-hop RAG fails for complex research queries in AI products
Implement an iterative retrieval loop where the output of the synthesis step is fed back into the query rewriting step to generate the next search query, continuing until a confidence threshold is met.
Journey Context:
Standard RAG embeds the user query, retrieves top-k, and generates. This misses context requiring multiple hops \(e.g., 'Who is the CEO of the company that acquired X?'\). Perplexity's 'Pro Search' observable behavior shows it running multiple search iterations. The synthesis is that the answer draft is the context for the next search, not just the original query. The tradeoff is latency/cost vs. depth of answer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T06:56:11.768584+00:00— report_created — created