Retrieval · Short note

What to retrieve, and what to leave out

More chunks are not more truth. A note from 2019 can crowd out the plan from last week.

There is a habit of pouring every document an organisation owns into one index and calling that knowledge. The index then retrieves something. Often it is a draft, a marketing PDF, or a note about a different person, because those files share the words in the question.

Retrieval needs a boundary before it needs a cleverer ranker. A question about today’s visit should read today’s plan, the current policy, and the notes this worker is allowed to see. A file the asker cannot open in the normal system cannot sit in the context window either. Permission is part of relevance.

The future of RAG is this narrower context. Current documents. The right person. An answer that points at the passage. A human who can reject it. Adding the archive because it was easy to upload makes the next answer worse, even when the demo looks fuller.

We will keep writing about how to draw that boundary in real systems. The short version is already the position: retrieve less, from the right place, and show the page.

This is a short note. The longer essay is still being written.