The gate lives in a pocket
A responder is walking a corridor, wearing gloves, holding something in the other hand. The approval card is designed for exactly that: one sentence, one clock, two buttons, thumb-reachable.
One sentence, then the numbers
The proposal opens with what will happen and why, in plain words. Confidence, signal traces and rule provenance sit one tap below for anyone who wants them.
A visible clock
The responder always knows how long they have and what happens when it runs out. There are no silent timeouts anywhere in the product.
Identity at the gate
Approvals are bound to a passkey on that handset, so a released action names a person and a device rather than a shared login.
Offline is normal
The phone talks to the gateway on the local network. A broadband outage does not stop a ward from answering its own approvals.
Escalation you can see
When a proposal moves up a tier, everyone in the chain sees where it went and why; no proposal ever quietly disappears.
Refusal is data
Every hold feeds back into the trust score for that rule. A rule people keep refusing loses the right to interrupt them.
Start with one ward, one shift, or one squad
A pilot runs four to sixteen weeks depending on deployment model. You bring the population and the responders. We bring devices, gateways and the first set of rules, and we measure override rate and time-to-answer from day one.