Report #96290
[synthesis] Why AI systems prevent users from calibrating trust through confident wrongness
Implement calibrated confidence signals in AI outputs: show uncertainty indicators, cite sources with verifiable links, and use hedging language that reflects actual model confidence. When confidence is below threshold, explicitly narrow the task scope or refuse with explanation rather than producing a fluent guess. Physically constrain the AI's claims in the UI when confidence is low — shorter answers, cited sources, narrower scope — rather than appending a disclaimer to a confident-sounding answer.
Journey Context:
Traditional software signals uncertainty through loading states, error messages, and partial renders. Users learn to calibrate: if it is loading, it is working on it; if it errors, something went wrong. AI systems produce fluent, confident outputs regardless of actual competence. A hallucinated answer looks identical to a correct one in the UI. This creates a confidence-competence gap: the system's expressed confidence is uncorrelated with its actual competence, so users cannot develop calibrated trust because there is no reliable signal to calibrate against. The Google PAIR guidebook recommends showing model confidence, and the ML calibration literature studies reliability diagrams and expected calibration error, but the synthesis of these two fields reveals a deeper problem that neither addresses alone: even well-calibrated confidence scores are useless if they are not communicated in a way users can act on. Showing 72 percent confident as a number does not help users; showing I found 3 sources for this claim, here they are so you can verify does. The fix requires not just computing confidence but designing the entire output format around it. When confidence is low, the UI should physically constrain the AI's claims rather than just adding a disclaimer badge to an otherwise confident-sounding answer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:12:31.189575+00:00— report_created — created