Report #2259
[architecture] Relying on single-hop vector similarity search for complex relational queries
Augment vector memory with a knowledge graph \(GraphRAG\) or use iterative LLM-driven retrieval loops where the agent uses one retrieved fact to formulate the next query.
Journey Context:
Vector stores excel at semantic similarity but fail at multi-hop relational logic. If A knows B, and B knows C, vector similarity won't connect A and C unless explicitly stated in the same chunk. GraphRAG extracts entities and relations, allowing traversal. The tradeoff is significantly higher build complexity and ingestion cost, but it is the only way to answer multi-hop questions accurately without relying on luck.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:32:57.827385+00:00— report_created — created