As of mid-2025, pure vector-based Retrieval Augmented Generation (RAG) has reached a performance ceiling. While effective for simple semantic recall, it fails spectacularly on schema-bound and multi-hop reasoning queries. This document outlines the uplift plan to transition Wikantik to a Hybrid GraphRAG architecture.
Recent evaluations using the Retrieval Experiment Harness confirm the industry-wide trend: Vector RAG accuracy collapses as query complexity increases.
| Query Complexity | Vector RAG | GraphRAG (Target) | Delta |
|---|---|---|---|
| Simple Factoid | 92% | 88% | -4% |
| Multi-Hop Reasoning | 22% | 78% | +56% |
| Global Theme Synthesis | 5% | 85% | +80% |
| Schema-Bound (e.g. KPIs) | 0% | 92% | +92% |
The "Graph Tax" (latency) is estimated at ~200ms per request, which is acceptable given the massive gains in precision.
The primary bottleneck is currently the quality of entity extraction. We will move from a "Chunk-First" to an "Entity-First" indexing model.
canonical_id to prevent graph fragmentation.The new pipeline will execute two parallel retrieval paths:
chunk_embeddings table.kg_edges table starting from identified entities in the query.The results are fused using Reciprocal Rank Fusion (RRF) before being presented to the LLM context window. This architecture is detailed in the Page Graph vs Knowledge Graph comparison.
To prevent regressions, the following controls will be implemented:
human-vetted or high-confidence ai-reviewed nodes will be admitted to the Path B retrieval loop.| Milestone | Target Date | Status |
|---|---|---|
| Baseline Benchmark | 2026-04-24 | [DONE] |
| Triplet Extractor Upgrade | 2026-06-01 | [PLANNED] |
| Hybrid Fusion Engine | 2026-07-15 | [PLANNED] |
| Production Cutover | 2026-08-30 | [PLANNED] |
This plan is managed by the Infrastructure & SRE team.