Report #6070
[architecture] Vector search fails on multi-hop reasoning questions
Augment vector memory with a knowledge graph \(GraphRAG\) or implement iterative retrieval loops where the agent extracts entities from the initial retrieval to formulate a secondary search query.
Journey Context:
Vector embeddings collapse meaning into a single point, losing relational structure. A question like 'Who is the manager of the person who wrote the document?' requires traversing edges, not just semantic similarity. The tradeoff is that graph construction and maintenance are significantly more complex than vector embedding, but it is strictly necessary for deep relational queries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T23:08:09.976593+00:00— report_created — created