Skip to main content
Guides + reports
PlaybookOperations· 12 min read

Setting up your first kill switch.

Who holds it, what triggers it, what it actually stops, and the monthly drill that keeps the muscle memory alive.

The kill switch is a per-store flag you own — off in normal operation, and when you flip it on, every worker job that writes or spends refuses to start. This playbook is about making it a control you trust rather than a button you've never pressed.

Decide who holds it

One named owner, plus one backup. In practice the best owner is whoever feels the consequences most — Head of Paid Media, Head of Retention, the founder. Ownership should sit with accountability, not with engineering.

Agree the triggers in advance

  • A metric moves in a way no one can explain yet — stop first, diagnose second.
  • An upstream platform is behaving abnormally and you don't want the agent reacting to bad data.
  • A high-stakes launch or sale where you want a human hand on everything for a day.

Run the monthly drill

  1. 1On a normal day, press the kill switch on purpose.
  2. 2Confirm new write jobs refuse to start — they show up as skipped runs in the job log.
  3. 3Verify in-flight actions were stamped in the decision_log and are reversible.
  4. 4Flip it back on. Total time: about five minutes.

A switch you've never tested is a hope, not a control. Drill it before you need it.

// no email gate

Want a guide written about your store?

We'll ghost-write the 'how we shipped Phase 2 in 14 days' case for any operator who flips Phase 2 inside their first month. Your data, your prose, our editorial bar.

Free to read · No email gate · Real read times