Report #102313
[synthesis] Output token entropy rises before error-rate dashboards move
Compute per-request lexical and semantic entropy of agent outputs; trend it by task type and alert on sustained increases that precede quality regressions.
Journey Context:
Error rate is a lagging indicator. Before the agent starts producing wrong answers, it often starts producing more hesitant, verbose, or internally inconsistent answers. Perplexity-style metrics and semantic variance within repeated or related outputs detect this. The challenge is that entropy naturally varies by task, so global thresholds fail. The fix is per-task baselines and change-point detection. Some teams reject this because it feels too theoretical, but it is one of the few signals that predicts failures before ground-truth labels arrive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:20:04.736128+00:00— report_created — created