Most retrieval-augmented generation (RAG) tutorials end at the same point: load some documents, split them into chunks, embed them, store them in a vector database and ask questions. That is enough for a demo. It is not enough for a system that a business relies on, because real documents change every day.
Policies get revised, product pages get updated, a contract gets replaced and an old one should no longer be quoted. If your index does not reflect those changes, your assistant will confidently answer with yesterday's facts. In my experience, stale or duplicated chunks cause more wrong answers than the language model itself.
The quick fix teams usually try is to rebuild the whole index every night. That works until the corpus grows, embedding bills climb and a nightly job fails halfway, leaving a half-built index in production.…