Best architecture for a chatbot over a frequently-updated company knowledge base?
Fine-tuning teaches behavior and style, not facts. For a knowledge base that updates daily, RAG is the architecture; a light fine-tune only adds voice on top.
Picture a brilliant new hire on their first day. Fine-tuning is the onboarding that shapes how they speak, format reports, and follow company policy. It changes their habits, not the facts in the filing cabinet. RAG is letting them open the cabinet and read the current file before answering each question. If the prices changed yesterday, you do not re-onboard the hire overnight; you just update the file they read. Trying to cram every fact into their head through training is slow, gets stale instantly, and they start half-remembering details and making things up. So you train the habits once and let them look up the live facts every time.
Detailed answer & concept explanation~8 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
4 min: misconception that fine-tuning teaches facts + what gradient updates actually encode + why facts in weights confabulate + RAG as the freshness layer + why each distractor fails + the layered production stack.
| Concern | Fine-tuning for facts (wrong tool) | RAG (right tool) |
|---|---|---|
| What it actually teaches | Behavior, style, format, reasoning patterns | Nothing new in the model; supplies fresh text to read |
| Daily knowledge update | Full retrain cycle (data, train, eval, deploy) | Re-embed changed chunks in seconds |
| Fact reliability | Partial memorisation, confident confabulation | Grounded in retrieved source with citations |
| Side effects | Catastrophic forgetting on narrow corpora | Retrieval latency and token cost per query |
| Cost to stay fresh | Repeated expensive retraining, still stale between runs | Cheap reindex, always current |
Real products, models, and research that use this idea.
- Perplexity grounds answers in live retrieval over web results rather than fine-tuning facts into a model, pairing retrieval with lightly tuned Claude Opus 4.7 and GPT-5.5 for citation-style synthesis.
- Glean and other enterprise search copilots index company wikis, tickets, and docs for RAG, then apply a thin fine-tune only for house voice and refusal policy.
- OpenAI and Anthropic fine-tuning guides explicitly steer teams toward retrieval for knowledge and reserve fine-tuning for behavior, format, and tone.
- Together.ai reference stacks fine-tune a Llama 4 variant for domain reasoning, then retrieve fresh documents with a BGE-reranker rather than baking facts into weights.
- Notion AI and similar productivity assistants answer from the user's current workspace via retrieval, since yesterday's edits must be reflected without any retraining.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy is a single fact sample-inefficient to learn via fine-tuning while a style is sample-efficient?
QIf RAG retrieval keeps returning stale or wrong chunks, would fine-tuning the facts fix it?
QWhen does it make sense to fine-tune on top of a RAG system, and on what data?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Believing fine-tuning is how you teach a model new facts. Gradient updates teach behavior and format; facts crammed into weights go stale and turn into confident confabulation.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.