Triage a hallucination without chasing symptoms
Diagnose whether a hallucination came from source gaps, prompt ambiguity, retrieval failure, or review controls.
Incident The FAQ assistant told a customer the enterprise plan includes 50 seats. The current pricing page says custom seat count only. A confident unsupported claim reached a live customer conversation. Root cause Five Whys for prompt-ops failures Do not stop at "the model hallucinated." Trace the bad output to the failed control: source, instruction, retrieval, review, or action boundary. Symptom Add "do not hallucinate" and hope. A fix aimed at the control, not the embarrassment. Every bad answer should map to a broken or missing control. 01 Evidence 02 Control 03 Fresh case Find the first why You inspect…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in