Report #3340
[architecture] Retrieval only finds directly relevant chunks and misses multi-hop connections
Use a graph memory layer \(entities → relations → entities\) alongside vector chunks so the agent can follow chains across documents and sessions.
Journey Context:
Vector search retrieves chunks similar to the query, but cannot answer questions like 'Which customer had the same issue last quarter?' if those words never appear together. A knowledge graph built from extracted entities and relations enables multi-hop reasoning. It costs more storage and indexing effort but unlocks causal chains.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T16:32:36.398860+00:00— report_created — created