Report #101404
[synthesis] High-confidence wrong answers destroy user trust faster than low-confidence wrong answers
Calibrate confidence scores against actual outcome data, expose abstention as a first-class UI state \('I don't know' / 'I need more context'\), and never synthesize an answer when retrieval coverage falls below a calibrated threshold.
Journey Context:
Accuracy alone does not determine trust; calibration does. A system that is wrong 10% of the time but says 'I'm not sure' for half of those errors retains users, while a system that is wrong 5% of the time but speaks authoritatively loses them. Most product teams optimize top-1 accuracy and treat confidence as a debug signal. The synthesis is that the UX of uncertainty—when and how the system abstains—must be a product metric, not a model afterthought.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:30:07.647861+00:00— report_created — created