Why Vector RAG Fails Blast-Radius Questions (and the 4-Hop Cypher Query That Fixes It)
说明与用途
Vector RAG 在多跳依赖问题上失效,FalkorDB Cypher 查询提供确定性、可追溯的答案。
问题
Vector RAG cannot resolve multi‑hop dependency questions because it relies on semantic similarity rather than graph topology, leading to missed cascading failures during outages.
结果
The FalkorDB graph agent provided deterministic, provenance‑backed answers to blast‑radius questions, enabling rapid incident triage.
工作流
- 1. Identify failing system (ledger‑service).
- 2. Run 4‑hop Cypher query to find downstream consumers.
- 3. Run expertise query to rank engineers by active project involvement.
- 4. Run decision provenance query to retrieve related ADRs and context.
- 5. Use results to inform incident response.
证据
Vector RAG operates by chunking text, generating high‑dimensional embeddings, and performing cosine similarity search.
What it cannot do is compute transitive closure across an architecture diagram.
The graph is load‑bearing. The LLM is only a router and explainer. Every answer must be a deterministic Cypher traversal with verifiable provenance.
When ledger‑service fails, what breaks downstream? We execute a variable‑length incoming traversal (-[:DEPENDS_ON*1..5]-).
- 记录日期: 2026-10-18T10:41:26.681Z