Track 01 · Models & contextLesson 08 of 10
Answers with receipts: grounding and citations
Every claim traced to a source, checked in code, or the assistant says it can't.
- The FDE path · Stage 2 of 6
- 35 min read
- 60 min hands-on
- Pro
What you'll be able to do
01- Explain the difference between grounded and parametric answers, and between closed-book and open-book answering, in terms a compliance reviewer accepts.
- Design an answer contract: answer only from provided sources, cite at a verifiable granularity, abstain when unsupported, and handle conflicting sources.
- Choose a citation format and a provider citation feature for a given UI, audit and latency requirement.
- Implement post-generation attribution verification (exact and fuzzy span matching, numeric checks) and decide what happens when it fails.
- Defend the source metadata you carry (document ID, version, effective date, page) in a regulated-industry review.
Before you start
- Tokens, context windows and why answers go wrong: parametric knowledge, training cut-offs, position effects.
- System prompts that survive a regulated rollout: where the answer contract and refusal wording live.
- Typed output: schemas, validation and tool calls: citations as a typed schema; key ordering.
- Context on a budget: what to keep, compress and cut: how much evidence fits, and where it sits in the prompt.
The short version
A grounded answer is one whose facts come from sources you supplied, not from what the model absorbed in training. In an enterprise that distinction is the whole game: the source is current, authoritative and reviewable; the model's memory is none of those. So you write an answer contract (use only these sources, cite each claim, say "I can't find that" when the sources are silent), you make the model cite at a granularity a reviewer can check (document, version, page, quoted span), and then you verify the citations in code after generation, because a citation that looks right is not the same as a claim the source supports. When verification fails, the answer is repaired, reduced or withheld, never shipped as is. Finding the right evidence is Week 02's problem. Using it honestly is this one.
- Grounded means the facts trace to supplied sources. The model's parametric knowledge supplies language and reasoning, not policy facts.
- Abstention is a feature. "The policy doesn't say" is a correct answer when the policy doesn't say.
- A citation is a claim about a source, and it can be false. Verify spans and numbers after generation.
- Faithful is not the same as relevant or correct. Measure each separately.
- Carry version and effective date end to end, or you will cite superseded policy with perfect confidence.
Pro lesson
The rest of this lesson is in Pro.
The mental model, worked example, field note, failure table, exercise and self-check, with the voice tutor.
Pro opens next
Stage 2 · One trustworthy model call- 3 lessons, with the voice tutor
- Halden week 2 · The dirty data pack lands
- The lab kit, to run Halden weeks on your machine
Also in Pro
- Every stage and specialisation, in full
- Every lab and every role project
- Halden weeks 2–10, on your record
- Every drill, live in the playground
- All solutions, plus the server judge
- Lab Assistant and every Teach with AI