Report #102354
[synthesis] Safety guardrails silently kill utility by blocking legitimate requests, and the metric dashboard looks green
Measure and alert on under-refusal and over-refusal separately; audit a random sample of blocked outputs weekly; set a utility-recovery target, not just a harm-reduction target.
Journey Context:
Safety tuning often optimizes for 'no bad outputs,' but over-refusal is a hidden failure mode where valid use cases are rejected. Standard dashboards show fewer incidents but miss churn from users who conclude the product is useless. The correct tradeoff requires dual metrics and human audit of the blocked set, not just the allowed set.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:24:10.499426+00:00— report_created — created