← Field Notes

Field note · Retrieval architecture · June 2026

RAG in 2026: choose the least complex system that wins

Basic RAG, modular retrieval, GraphRAG and Agentic RAG solve different evidence problems. Architecture should be selected by task shape and evaluation results, not by whichever label is newest.

AudienceCTOs · founders · engineering leaders
PerspectiveProduction architecture and delivery
FormatOriginal analysis grounded in primary sources

Start with the question

Simple factual lookup over well-structured documents may need hybrid retrieval and reranking, nothing more. Multi-hop relationship questions can justify graph retrieval. Open-ended research may justify an agent that plans, searches, verifies and retries.

The retrieval-generation gap

Retrieving more information does not guarantee a better answer. Recent comparative research found that advanced retrieval can improve retrieval-oriented metrics without proportionate generation quality, while context optimisation can materially reduce token use.

A practical decision ladder

Begin with metadata filtering, hybrid lexical-vector retrieval, contextualised chunks and reranking. Add query decomposition or routing when evaluation reveals distinct query classes. Add graphs only for relationship-heavy questions; add agents only when adaptive multi-step evidence gathering produces measurable gains.

Production controls

Preserve source permissions, freshness and provenance. Measure retrieval recall, citation validity, groundedness, answer usefulness, latency and total cost. Include adversarial tests for poisoned, contradictory and access-restricted sources.

Executive takeaway

The best RAG architecture is the simplest one that meets the evidence standard. Complexity should buy measurable answer quality or risk reduction; otherwise it becomes an expensive demonstration.

Primary reading

  1. Is GraphRAG Needed? : comparative 2026 research
  2. Anthropic : Contextual Retrieval
  3. Agentic RAG survey