AI Operations · established evidence
The Internal Knowledge Problem: Why Retrieval-Augmented Generation Is Not the Same as an Agent That Knows Your Business
Retrieval-augmented generation, or RAG, is the technique that lets a language model answer from your documents instead of from its training data alone: at answer time the system fetches the passages it judges relevant and hands them to the model as context. It genuinely reduces one failure mode, the model inventing facts it was never shown. What it does not do is make the model understand your business, and it does not guarantee the answer is correct. Grounding is a supply of evidence, not comprehension. The model can retrieve the wrong passage, be handed a stale or poisoned one, cite a source it did not actually reason from, or fetch the right facts and still reason to a wrong multi-step conclusion. An agent that knows your business is one that retrieves the right thing, reasons over it correctly, does so consistently, and refuses when it should. RAG is a necessary part of that, not the whole of it.
Grounding is a supply of evidence, not comprehension
When people say an AI assistant is "grounded" in their business, they usually mean it has been connected to their real content: the service menu, the policies, the price list, the past tickets. Retrieval-augmented generation is the standard way to do that. Rather than fine-tune the facts into the model, the system stores your documents, and when a question arrives it retrieves the passages that look relevant and places them in front of the model as context to answer from.
This is a real improvement over an ungrounded chatbot, which answers from a frozen, general training set and will confidently fill any gap with a plausible invention. Feeding the model your own current documents removes a large class of those inventions. But it is worth being precise about what has changed. The model has been given evidence at answer time. It has not been given understanding of how your business works, what it means for two policies to conflict, or which of three retrieved snippets actually governs the case in front of it. Grounding narrows what the model can get wrong. It does not make the model right.
What retrieval-augmented generation actually does, step by step
The pipeline is mechanical, and understanding the steps is what makes its limits legible. Your documents are split into chunks and converted into numeric vectors called embeddings, which are stored in a vector database. A question is converted the same way, and the system returns the chunks whose vectors sit closest to the question's vector. Those retrieved chunks, not your whole knowledge base, become the context the model reads before it writes a word.
Two things follow directly from that design. First, the model only ever sees what retrieval hands it, so a retrieval miss is invisible to the model and to the reader: the answer looks just as fluent whether the right passage was fetched or not. Second, "closest vector" is a similarity heuristic, not a judgment about which passage is authoritative, current, or correct for this specific customer. The quality of a grounded answer is therefore capped by the quality of retrieval, and retrieval is the part of the system most businesses never inspect.
Why grounded still is not the same as correct: vector and embedding weaknesses
The security community has already catalogued where this breaks. In its 2025 edition, the OWASP Top 10 for LLM Applications promoted Vector and Embedding Weaknesses to entry LLM08 specifically because retrieval-augmented generation has become the dominant pattern, and the retrieval layer introduced new attack and failure surfaces that did not exist in a plain chatbot.
Concretely, that category covers retrieval returning the wrong or an outdated chunk; embeddings that blur two distinct records together so the model answers about the wrong one; and data poisoning, where content placed in a source the system ingests steers the answer. Related to it, Prompt Injection has stayed at number one across both the 2023 and 2025 editions, including its indirect form, where hidden instructions ride inside external content the model processes, exactly the content a RAG system is built to read. A grounded agent that ingests documents, web pages, or past emails is, by construction, reading text that an outsider may have written. Retrieval widened the mouth of the system, and that is a capability and a liability at once.
Retrieval fixes the facts it fetches, not the reasoning over them
Even when retrieval hands over the correct passages, the model still has to reason across them, apply your policy, and act. That is where the benchmark evidence is sobering. In the peer-reviewed tau-bench study, researchers tested tool-using agents against simulated customers and real tool APIs under domain policy constraints in retail and airline customer-service settings. Agents built on capable models, using standard constructs like function calling, succeeded on fewer than half of realistic tasks.
The consistency finding is the one that matters most for a business. When the identical task was repeated eight times, the same agent completed it correctly only about a quarter of the time. Reliability was worse than the raw success rate suggested, because the agent would solve a task on one run and fail the same task on the next. No amount of grounding addresses that: the facts were available, the failure was in reasoning and execution over them. "Knowing your business" means correctly handling the multi-step case, the exception, and the policy conflict, over and over. Retrieval alone does not deliver that, which is why a grounded agent still needs an evaluation suite and a defined scope of what it is allowed to decide.
The hallucination-reduction number you should not trust
It is tempting to attach a single figure to all this, some clean "RAG cuts hallucinations by X percent" headline. No single number holds up across studies. Reported hallucination-reduction rates for retrieval-augmented generation vary widely by study, by domain, by which model was tested, and by how "hallucination" was even defined. A number that is true for a legal-document benchmark may be meaningless for a med-spa booking flow. Quoting one as if it were a universal law misrepresents what the research shows.
The defensible claim is qualitative and well supported: grounding reduces fabricated-fact errors relative to an ungrounded model, and it does not eliminate error, because retrieval, reasoning, and citation can each fail independently. If you want a number for your own situation, the only reliable one comes from measuring your own system: building an evaluation set from your real questions paired with your own approved answers, then scoring the live agent's responses as right, wrong, or invented. A benchmark like tau-bench tells you the shape of the risk. Only a test on your own content and policies tells you its size.
You own what your grounded agent says
The stakes are not academic, because the liability is already settled in at least one adjudicated case. In Moffatt v. Air Canada, a civil tribunal held the airline responsible for incorrect information its website chatbot gave a customer, ruling that a company is responsible for all the information on its site whether it came from a static page or a chatbot, and rejecting the argument that the bot was a separate legal actor.
The regulatory line points the same way. In its Operation AI Comply actions, the U.S. Federal Trade Commission moved against companies making unsubstantiated claims about their AI, including a self-described "robot lawyer" whose output no attorney had ever reviewed and whose generated documents had never been tested for validity; the final order barred it from claiming professional-grade performance without evidence. The common thread for a small business is direct: a grounded agent that answers wrong is still your statement to your customer, and "the AI said it" is not a defense. That is precisely why a knowledge agent needs a refusal boundary, a rule that it says it does not know and hands off to a person rather than guess, built in before it ever faces a customer.
What it takes to build an agent that actually knows your business
The gap between a demo and a dependable system is the reason most deployments disappoint. MIT NANDA's 2025 study of enterprise generative-AI deployments found that the great majority of pilots produced no measurable profit-and-loss impact, and attributed the gap not to weak models but to tools that could not retain feedback or adapt to a business's context. That is the same lesson in a different register: connecting a model to your documents is the start of the work, not the end of it.
A knowledge agent that earns trust is engineered, not bolted on. It runs on a curated corpus of your approved content rather than the open web. It is built to cite the specific source behind each answer, so a claim can be checked. It carries an explicit refusal boundary. It is measured against a set of your real questions with known-correct answers before launch, and monitored on a cadence afterward, because a system that answered cleanly in January can start hedging or inventing by April with nothing throwing an error. Grounding through retrieval-augmented generation is one component of that system. Sold as the whole of it, it is a promise the technology does not keep.
Reading the evidence
The accurate position sits between two oversold stories. It is not true that retrieval-augmented generation is a gimmick that changes nothing, and it is not true that grounding a model on your documents makes it a reliable expert in your business. The measured reality, drawn from OWASP's catalogue of retrieval weaknesses and tau-bench's reliability findings, is that grounding meaningfully lowers one kind of error while leaving retrieval quality, reasoning consistency, citation faithfulness, and scope of authority as separate problems that each need their own control.
For an owner deciding whether to trust an AI assistant with customer-facing answers, the useful question is not "is it grounded" but "how do we know what it can and cannot reliably say, and what happens when it does not know." Those are answerable questions. They are answered by measurement and by design, not by the word "grounded" on a sales page.
The evidence
Key findings, with their sources
-
Tool-using agents built on capable models succeeded on fewer than half of realistic customer-service tasks under domain policy constraints; repeating the identical task eight times, the same agent succeeded only about 25% of the time.
established Yao et al., "tau-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains", arXiv:2406.12045, 2024 (Sierra Research).
-
The 2025 OWASP Top 10 for LLM Applications promoted Vector and Embedding Weaknesses to entry LLM08 specifically because of the rise of retrieval-augmented generation, and kept Prompt Injection (including its indirect form via external content the model reads) at number one across both the 2023 and 2025 editions.
established OWASP Foundation, "OWASP Top 10 for Large Language Model Applications", 2025 edition (owasp.org, GenAI Security Project).
-
A company is responsible for all the information on its site "whether it came from a static page or a chatbot"; the tribunal rejected the argument that the chatbot was a separate legal actor and held the airline liable for its incorrect answer.
established Moffatt v. Air Canada, 2024 BCCRT 149 (British Columbia Civil Resolution Tribunal, 2024-02-14).
-
The great majority of enterprise generative-AI pilots produced no measurable profit-and-loss impact, a gap attributed to organizational adoption and to tools that could not retain feedback or adapt to context rather than to model quality.
established MIT NANDA, "The GenAI Divide: State of AI in Business 2025", 2025-08 (survey and case-study based; treat as directional).
-
74% of organizations now cite inaccuracy as their top AI-related risk, up 14 points in a single year, ahead of cybersecurity, regulatory compliance, and privacy.
established Stanford HAI, "The 2026 AI Index Report", hai.stanford.edu/ai-index/2026-ai-index-report.
-
The FTC ordered a self-described "robot lawyer" to stop claiming professional-grade performance without evidence; the company had never had an attorney review its output or tested whether its generated documents were valid.
established U.S. FTC, "Operation AI Comply" and the finalized In re DoNotPay order, 2024-09 through 2025-01.
Calibration
What is proven, what is promising, what is unproven
| Evidence tier | Tactics | What the evidence says |
|---|---|---|
| established | Retrieval weaknesses are real and catalogued; agent reliability is measurably low and inconsistent; a business is legally accountable for what its deployed AI says. | OWASP LLM Top 10 2025 (LLM08, Prompt Injection); tau-bench (arXiv:2406.12045); Moffatt v. Air Canada 2024 BCCRT 149; FTC Operation AI Comply. |
| established (directional) | Most AI pilots fail to show measurable financial impact, and the cause is adoption and context-fit, not raw model quality. | MIT NANDA, State of AI in Business 2025 (survey and case-study methodology; conclusions are directional, not causal). |
| contested / needs primary data | Any single "RAG reduces hallucinations by X percent" figure applied across businesses. | Reported reduction rates vary widely by study, domain, model, and definition; not independently verifiable as a universal number. The only reliable figure comes from measuring your own system. |
Reference
Glossary
- Retrieval-augmented generation (RAG)
- A technique in which a system fetches relevant passages from your own documents at answer time and supplies them to a language model as context, so the model answers from your content rather than from its training data alone.
- Grounding
- Connecting a model's answers to specific external evidence (your documents) instead of letting it answer from memory. Grounding supplies evidence; it does not supply understanding.
- Embedding / vector database
- An embedding is a numeric representation of a chunk of text; a vector database stores those numbers so the system can retrieve the chunks most similar to a question. Similarity is a heuristic, not a judgment of authority or correctness.
- Hallucination
- A fluent, confident AI answer that is not supported by any real source. RAG reduces the fabricated-fact kind of hallucination but does not eliminate error from wrong retrieval or wrong reasoning.
- Faithfulness
- Whether an answer is actually supported by the sources it draws on or cites. A citation being shown is not proof the model reasoned from it.
- Refusal boundary
- An explicit rule that an agent says it does not know and hands off to a person rather than guess, when the retrieved evidence does not support a confident answer.
- Indirect prompt injection
- A manipulation where hidden instructions are placed inside external content the model reads, the same content a retrieval system is designed to ingest, causing the model to follow the attacker's instruction.
Straight answers
Frequently asked questions
What is retrieval-augmented generation (RAG)?
It is the standard method for letting an AI answer from your own documents. Instead of relying on the model's general training, the system stores your content, retrieves the passages most relevant to a question, and gives them to the model as context to answer from. It reduces the model inventing facts it was never shown.
Does RAG stop AI hallucinations?
No. It reduces one kind, the model fabricating facts, by supplying real evidence, but it does not eliminate error. Retrieval can fetch the wrong or outdated passage, and the model can still reason incorrectly over the right passage. Grounding lowers the risk; it does not remove it.
Is a RAG-grounded agent the same as an agent that knows my business?
No. Grounding gives the model evidence at answer time; it does not give it understanding of how your business works, which policy governs an exception, or how to handle a multi-step case consistently. Benchmark evidence shows capable agents fail more than half of realistic tasks and are inconsistent when the same task is repeated. Knowing your business means retrieving the right thing, reasoning correctly, doing it reliably, and refusing when it should.
What is the real hallucination-reduction rate with RAG?
There is no single reliable number. Reported rates vary widely by study, domain, model, and how hallucination is defined, so any universal percentage is misleading. The figure that matters is the one measured on your own content, by testing the live system against your real questions with known-correct answers and scoring each response as right, wrong, or invented.
How do I know if my knowledge agent is giving customers wrong answers?
You measure it rather than assume it. Build an evaluation set from your actual questions paired with your approved answers, run it through the live agent, and record the rate of correct, incorrect, and invented responses. Because systems drift, that check needs to run on a cadence, not once at launch.
Provenance
Sources
- Yao, S. et al., "tau-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains", arXiv:2406.12045, 2024 (Sierra Research) (established)arxiv.org
- OWASP Foundation, "OWASP Top 10 for Large Language Model Applications", 2025 edition, owasp.org GenAI Security Project (established)
- Moffatt v. Air Canada, 2024 BCCRT 149, British Columbia Civil Resolution Tribunal, 2024-02-14 (established)canlii.org
- MIT NANDA, "The GenAI Divide: State of AI in Business 2025", 2025-08 (established; survey and case-study methodology, directional)
- Stanford HAI, "The 2026 AI Index Report", hai.stanford.edu/ai-index/2026-ai-index-report (established)hai.stanford.edu
- U.S. Federal Trade Commission, "Operation AI Comply" enforcement actions and In re DoNotPay final order, 2024-09 through 2025-01 (established)
- Anthropic, "Building Effective AI Agents", 2024-2025, anthropic.com/research/building-effective-agents (established; used for the workflow-versus-agent distinction)
Every figure above is attributed to a real, dated source and tagged with its evidence tier. Where a claim could not be verified to a primary source, it is not stated as fact.