Speech ML/AI Production Incident Drills

Mitigate by rolling back the decoder or raising partial-stability thresholds for affected routes. Slice by utterance duration, endpoint VAD state, beam size, language, device, and network jitter. Look for changed emission timing, punctuation instability, hotword biasing, or aggressive rescoring. Add partial churn, first stable token latency, and finalization delay to release gates; final WER alone is not enough for streaming UX.

Mitigate with fallback voice routing, shorter first sentence chunks, warm pools, or canary rollback. Slice text length, language, voice, region, vocoder path, cache hit rate, autoscaling cold starts, and queue depth. Prevention needs conversational latency gates, not only MOS or preference tests. Track first audio byte, chunk cadence, playback underruns, cost per generated minute, and abandonment.

Mitigate by pinning the previous index, disabling affected document namespaces, or forcing human handoff when retrieval confidence is weak. Slice by document version, embedding model, chunker, ASR error class, query language, and top-k overlap with the old index. Add retrieval regression tests from spoken queries, citation coverage, answer-grounding checks, and index lineage to the release gate.

Pause rollout or route the affected slice to the stronger model. Compare WER, entity error rate, confidence calibration, correction rate, and escalation rate by accent proxy, SNR bucket, duration, device, and domain. A staff-level tradeoff may keep a tiered model router, but only if slice quality and fairness gates are explicit. Add cost-quality frontier reviews instead of aggregate-only cost wins.

Mitigate by reverting the SDK, disabling full-duplex mode, or routing to push-to-talk for affected clients. Slice by SDK version, device, echo cancellation state, VAD endpointing, playback state, and event ordering between microphone frames and TTS cancellation. Prevention needs end-to-end turn-taking tests with overlapping audio, not only component health checks.

Mitigate with slice-specific routing, contextual language hints, or rollback of the regional launch path if quality is below contract. Monitor aggregate feature drift, language-id distribution, OOV rate, correction rate, fallback rate, and human escalation. Use privacy-safe aggregates and governed samples. Prevention needs traffic-mix drift alerts tied to eval coverage, not just model metric dashboards.

Invariant: each slice is compared only against its own baseline. Test missing baseline, missing metric, exactly-on-budget deltas, lower-is-better metrics like WER, and higher-is-better metrics like task success.

def rank_regressions(baseline, candidate, budgets):
    findings = []
    for slice_name, metrics in candidate.items():
        old = baseline.get(slice_name)
        if old is None:
            findings.append((float("inf"), slice_name, "missing_baseline", None))
            continue

        for metric, rule in budgets.items():
            if metric not in metrics or metric not in old:
                findings.append((float("inf"), slice_name, metric, "missing_metric"))
                continue

            delta = metrics[metric] - old[metric]
            allowed = rule["allowed_delta"]
            direction = rule["direction"]
            if direction == "lower_is_better":
                severity = delta - allowed
            else:
                severity = -delta - allowed

            if severity > 0:
                findings.append((severity, slice_name, metric, delta))

    return sorted(findings, reverse=True)

Invariant: user harm overrides aggregate wins. Test high SLO burn, one critical slice, many noncritical warnings, and a clean canary with cost or latency improvement.

def recommend_rollout(slo_burn, critical_regressions, warnings, aggregate_wins):
    if slo_burn >= 2.0:
        return "rollback", "SLO burn is too high"
    if critical_regressions:
        affected = sorted({item["slice"] for item in critical_regressions})
        if len(affected) <= 2:
            return "partial rollback", "route affected slices: " + ", ".join(affected)
        return "rollback", "critical regressions are broad"
    if len(warnings) >= 3:
        return "pause", "too many unresolved warning signals"
    if aggregate_wins:
        return "continue", "wins are acceptable and guardrails are clean"
    return "pause", "no clear win yet"

Invariant: the output contains counts, versions, and metric summaries only. Test that transcript, audio path, user id, and raw text fields never appear in the packet.

from collections import Counter, defaultdict


def incident_packet(records):
    counts = Counter()
    latency = defaultdict(list)
    versions = Counter()

    for row in records:
        key = (row.get("language", "unknown"), row.get("device", "unknown"))
        counts[key] += 1
        if "latency_ms" in row:
            latency[key].append(row["latency_ms"])
        if "model_version" in row:
            versions[row["model_version"]] += 1

    latency_summary = {}
    for key, values in latency.items():
        values = sorted(values)
        p95_index = int(0.95 * (len(values) - 1))
        latency_summary[key] = {
            "count": len(values),
            "p50_ms": values[len(values) // 2],
            "p95_ms": values[p95_index],
        }

    return {
        "slice_counts": dict(counts),
        "latency": latency_summary,
        "model_versions": dict(versions),
    }

Roll back when user harm is active, SLO burn is high, privacy or safety is at risk, or the blast radius is not understood. Fix forward only when the failure is narrow, the mitigation is lower risk than rollback, validation is fast, and fallback remains ready. Mention model version flags, canary scope, eval slices, owner approval, and post-incident release-gate changes.

Include turn latency, first partial latency, finalization delay, TTS first audio byte, barge-in success, ASR confidence, retrieval grounding, answer safety, fallback/handoff, cost per minute, error budget burn, and slice drift. Page on customer-impacting SLO burn, safety/privacy failures, broad fallback spikes, and sustained groundedness collapse; ticket lower-severity drift and cost trends.