Report #60775
[architecture] Assuming a single vector search is enough to answer complex questions requiring connecting multiple distinct facts
Implement iterative retrieval \(e.g., ReAct pattern\) where the agent uses the result of one retrieval to formulate the next query, chaining lookups across hops.
Journey Context:
A user asks 'What was the bug we fixed right after the DB migration?'. A single vector search for 'bug after DB migration' fails if the memory of the bug doesn't explicitly mention the migration. The agent needs to first retrieve 'DB migration', find the date, then search for 'bugs fixed on \[date\]'. Single-hop RAG fundamentally cannot resolve multi-hop dependencies; the agent must be allowed to reason and retrieve iteratively.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:29:49.590331+00:00— report_created — created