Kill switch before you scale an LLM
A kill switch is a written, rehearsed way to stop or throttle the LLM surface when quality, cost, or abuse crosses a line. Without it, “we will watch the dashboard” is not a production gate.
Minimum viable kill switch
- Owner and on-call path named
- Trigger thresholds (quality, refusal, cost, latency, abuse) written
- Action: disable route, force human handoff, or fall back to a safe template
- Log what fired and when, for the next review
Pair it with a regression suite. A switch you never test is theatre.
Arviser deliverables
Readiness and Audit both push for an explicit kill or continue path. The Evidence Pack outline includes a kill-switch section you can fill before counsel or leadership review.
Next: Evidence Pack · Checklist · CI gates · Request scope