Report #24505
[synthesis] AI feature works perfectly until it suddenly fails catastrophically on edge cases — capability cliff
Implement confidence-based routing with deterministic fallbacks. Measure and monitor model calibration — how well predicted confidence matches actual accuracy. Route low-confidence predictions to fallback paths \(templates, search, human handoff\) before users encounter failures. Never surface raw model outputs without a confidence gate.
Journey Context:
Traditional software degrades somewhat gracefully — missing features, slower performance, partial functionality, informative error messages. AI often has a capability cliff: it performs well within its training distribution and catastrophically fails outside it, with no gradual degradation warning. Worse, modern neural networks are systematically miscalibrated — they express high confidence on wrong answers, especially on out-of-distribution inputs. This means the capability cliff is invisible to both the user and the system until the failure happens. The fix is to treat model confidence scores as routing signals, not just display information. When confidence drops below a calibrated threshold, route to a deterministic fallback. This requires investing in calibration: ensuring the model's confidence scores actually predict its accuracy, using methods like temperature scaling or Platt scaling. Tradeoff: aggressive confidence thresholds reduce automation rates and increase fallback costs \(especially human handoff\), but they prevent the catastrophic failures that destroy user trust asymmetrically and are much more expensive to recover from.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:32:31.483100+00:00— report_created — created