1. Why RAG in Late 2026: The Stack Moved, the Debate Did Not

Every few months a blog post announces that RAG is dead — that long-context models, prompt caching, or agentic search have made retrieval pipelines obsolete. The discourse is real: Hacker News spent the spring of 2026 arguing through threads like Is RAG Dead? Long Context, Grep, and the End of the Mandatory Vector DB. The claim is half right, and the half that is right matters for architecture: naive chunk-and-embed RAG is dead. Retrieval engineering is not. The pipeline your platform team runs in production just looks nothing like the 2023 tutorial.

What actually changed in the last quarter is the retrieval stack itself, and all of it is verifiable from primary sources:

  • Qdrant v1.20.0 (October 22, 2026) added BM25 scoring directly on the full-text payload index, which means one database now serves the dense and the lexical side of hybrid retrieval without a separate Elasticsearch cluster. The same release shipped TurboQuant (turbo8/turbo16 vector datatypes), fixed HNSW layer assignment to match the original paper (6.25% of points on level 1 at m = 16, down from 25% — smaller upper-layer graphs, less memory), and added hnsw_config.inline_storage to stop storing a second copy of vectors outside the graph file.
  • Cohere shipped Embed 5 (September 30, 2026) with a shared embedding space across the Pro and Fast variants — index once with Pro, query with Fast — 128k-token context, Matryoshka output dimensions from 256 to 2048, and int8/binary output types. Rerank 5 followed with a 32,768-token context window and calibrated 0–1 relevance scores.
  • Voyage AI's voyage-4 family (January 2026) made 1024 dimensions the default with configurable 256/512/2048 Matryoshka truncation, and released voyage-4-nano as an open-weight model on Hugging Face — the first time a frontier-tier embedding family has a self-hostable sibling.
  • RAGAS moved to vibrantlabsai/ragas and shipped v0.4.3 — the evaluation framework your team either already runs or is about to be asked for by an auditor.

Meanwhile, the economics shifted underneath: OpenAI's prompt caching now discounts cached input tokens up to 95%, with cache reads at 0.1× the ordinary input rate for GPT-5.6 and later, and Anthropic sells 5-minute cache entries at 1.25× write and roughly 0.1× read. That changes the small-corpus calculus enough that we will compute the exact crossover in section 9 — and the answer is not "RAG always wins." Spoiler: below roughly 225k tokens of stable, frequently-queried corpus, stuffing the whole thing into a cached prompt can be cheaper than the retrieval stack in front of a cheap generation model.

This guide is the reference architecture we would hand a platform team starting a production RAG pipeline in November 2026: chunking strategy, embedding model selection, vector store selection with exact configuration parameters, hybrid retrieval, reranking, an evaluation harness wired into CI, complete Kubernetes manifests, and a cost model computed from the live rate cards. Everything version-specific was verified against primary sources on November 10, 2026 — release notes, official docs, and pricing pages, not vendor blog posts.

2. Reference Architecture: Five Planes

A production RAG pipeline is five planes with different failure modes, different owners, and different cadences. The diagram below is the shape we will build through the rest of this guide.

                        ┌─────────────────────────────────────────────────┐
                        │              GOVERNANCE PLANE                   │
                        │  git = source of truth · index registry          │
                        │  tenant policy · eval thresholds in CI          │
                        └───────────────┬─────────────────────────────────┘
                                        │ config + gates
        ┌───────────────────┐   ┌───────▼────────┐   ┌──────────────────────┐
        │  INGESTION PLANE  │   │  INDEX PLANE   │   │    EVALUATION PLANE  │
        │───────────────────│   │────────────────│   │──────────────────────│
        │ source connectors │   │ Qdrant 1.20    │   │ golden dataset       │
        │ parse (PDF/MD/    │──▶│ dense (HNSW)   │◀──│ RAGAS 0.4.3 metrics  │
        │  code/wikis)      │   │ sparse (BM25   │   │ recall@k · MRR        │
        │ chunker           │   │  payload index) │   │ CronJob in K8s       │
        │ contextualizer    │   │ payload indexes│   │ CI gate on regress   │
        │ embedder          │   │ (tenant, src)  │   └──────────────────────┘
        │ upsert batches    │   └───────▲────────┘
        └───────────────────┘           │ points + payload
        runs on: Job / CronJob           │
        cadence: hourly/daily   ┌────────┴────────────┐
                              │   RETRIEVAL PLANE    │
                              │──────────────────────│
                              │ query embed          │
                              │ hybrid: dense + BM25 │
                              │ RRF fusion           │
                              │ rerank top-150→20   │
                              │ assemble context     │
                              │ ─────────────────── │
                              │ serves: Deployment  │
                              │ +HPA, p99 budget    │
                              └────────┬─────────────┘
                                       │ top-k chunks
                                       ▼
                              ┌─────────────────────┐
                              │  GENERATION (LLM)   │
                              │ prompt-cached prefix│
                              └─────────────────────┘