Why it matters
Traceability connects an answer to retrieval sets, policy decisions, model version, and source versions. Incidents without traceability devolve into blame storms.
How it works
Persist structured logs per answer: query, filters, chunks, policy outcomes, output, citations. Retain per compliance policy. Expose to support tools.
Example
Nintendo traceability shows a wrong tax answer used an outdated Help Center footnote chunk indexed before a policy fix. Support replays the exact retrieval path in minutes.
Common mistakes
- 1Logs missing model or prompt version
- 2Retention too short for billing disputes
- 3Trace data inaccessible to frontline support
Test the answer before your customer does.
Run answer tests and evaluations against your governed knowledge before you ship.
See answer evaluations