Report #42707
[architecture] Raw LLM confidence scores are miscalibrated for routing decisions
Calibrate confidence scores using temperature scaling or isotonic regression on a hold-out validation set; set decision thresholds \(e.g., auto-approve >0.9, human-review 0.7-0.9, reject <0.7\) based on empirically measured precision-recall tradeoffs.
Journey Context:
Developers often use raw log-probabilities or arbitrary 'confidence' keywords from LLMs to route tasks. These scores are poorly calibrated—an 80% confidence may actually correspond to 50% accuracy. Simply thresholding at 0.5 fails. The fix comes from supervised learning calibration literature: fit a post-hoc calibration model \(Platt scaling, isotonic regression\) on a representative validation set to map raw scores to true probabilities. Then set thresholds based on business cost of false positives vs false negatives. This is often skipped because it requires labeled validation data and offline analysis, but without it, automated routing is statistically unreliable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T02:09:08.854927+00:00— report_created — created