Report #13193
[architecture] Expecting a single vector search to answer complex queries requiring connecting multiple distinct facts
Implement iterative retrieval \(search -> extract -> search\) or use GraphRAG to traverse relationships between entities.
Journey Context:
Vector databases perform cosine similarity on a single chunk of text. If the user asks 'Who is the manager of the person who wrote the auth module?', a single search will likely fail because the author and the manager are in different chunks. Naive RAG just does one retrieval. The fix is allowing the agent to loop: retrieve the author, then retrieve the manager. GraphRAG is an alternative for pre-computed relationships.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T18:09:34.297336+00:00— report_created — created