The model is only as good as the context you hand it. Most RAG stacks hand it duplicates, superseded drafts, and irrelevant spans - noise that makes answers worse and makes cost creep up as your data grows. SWIRL builds a cleaner prompt: one canonical answer, only the passages that matter. We measured it against the common stacks, checked it against their own source, and here is the honest result.
Over a realistic enterprise corpus, where the relevant policy exists in five versions plus three other documents, here is how many input tokens each stack actually sends the model to answer one query. Fewer tokens here means less redundant noise reaching the model - and a cost that stays predictable as the corpus grows.
Fig. 1 Same question, same corpus; what each stack actually hands the model. Full methodology in the study PDF.
One question fans out across your systems, SWIRL clusters the versions it finds, and elects the canonical one. The model reads that, not five near-identical drafts.
This version election is what removes the duplicate-version tokens from the chart above. Fewer copies to the model means an answer grounded in the right document - and a cost that stays predictable as the corpus grows.
Off-the-shelf top-k returns whatever is nearest in embedding space; in a versioned corpus, that is several near-identical copies. Handing all of them to the model invites a confident answer built on a superseded draft. SWIRL collapses them first, so the model reads the one your team approved.
The prompt is built to a budget and answered in a single call - no refine or tree-summarize mode calling the model once per chunk. One call, one generation, a cost per answer that does not balloon as your documents and corpus grow. That is the token question enterprises actually ask: not "is it cheap," but "is it predictable."
A relevance matcher scores the spans inside each source and sends those, marked up and fitted to the budget. The model gets more signal, not more tokens - higher grounding than stuffing raw chunks, so the answer improves and you are not paying to send the model noise.
Straight about the trade-off: a carefully hand-tuned vanilla RAG (low k, a good reranker, small chunks, plus your own de-dup layer) can match SWIRL's per-call token count. SWIRL's value is delivering that discipline by default, and collapsing document versions the way off-the-shelf stacks do not. It is not magic per-token compression, it is better engineering, out of the box - so the answer is grounded in the right document and the cost stays predictable.
Source-checked against LangChain and LlamaIndex code, vendor RAG tutorials, and the SWIRL 5 source. One page, no form, no email required.
Download the study (PDF)