Microsoft measured GraphRAG beating vector RAG on 72-83% of sense-making questions. Microsoft then shipped LazyGraphRAG, which indexes at 0.1% of that cost. When the vendor builds the cheap version, the expensive version's price was the finding. Here is where a graph actually earns its keep, and the hybrid most teams land on instead.
BM25 plus embeddings, then a cross-encoder over the top-k. The two stages buy different things and most teams cannot say which one they added. Hybrid search buys recall because lexical and vector retrieval fail on different queries; reranking buys precision because a cross-encoder reads the query and the document together. Here is what each one measurably adds, and how to tell when the reranker is buying you a rounding error.
Fixed-size, semantic, and structure-aware chunking measured against real retrieval failures. The uncomfortable finding: your chunking choice barely moves whether the answer reaches the model, and hugely moves how much junk you pay for to get it there. Also, your chunk size is probably a library default nobody chose.
Vector search over data you could have queried with SQL is the most common architecture smell in agent systems. It is slower, less accurate, more expensive to maintain, and it fails in a way that is hard to detect. Here is the decision rule.