Eleven behaviours, one core
Strip the vocabulary away and every industry asks for the same things. A ward, a yard, a wing and a wharf all need duress answered, people accounted for, and evidence that stands up later. Every pack is a different vocabulary over the same eleven behaviours. Enable a subset and you inherit the rest as latent capability, on the same tags, the same infrastructure, the same core.
What recurs everywhere
Safety and evidence themes run on the shipping core today. Themes that lean on analytics capability are not listed here at all, because breadth is a claim and we only make the ones we can demonstrate. The full specified catalogues, 712 use cases across fifteen industries, sit on the industry pages.
Mobile duress
A person in trouble presses once, from a badge, a pendant or the handset app, and help is on the way.
Every raise is P1 at origination, nothing can downgrade it, and no rule or licence state sits in the alarm path.
Fixed duress & help points
Buttons, pull cords and panic points at counters, interview rooms and cash offices, wired straight into the same runtime.
A fixed point enters the identical alarm path as a wearable: no de-duplication, no inference, a human decision every time.
Man-down & no-motion
A device that detects a fall or a stillness that should not be still raises help without a button press.
The signal is treated as a duress, not a data point. It rides the closed-loop escalation ladder that never silently lapses.
Lone worker
Staged protection for the person working alone. Prime on entering a risky situation, trigger with one action.
No time limit between the two, and the responder's own position travels with the response.
Evacuation, muster & roll-call
When the building empties, the question is who isn't at the muster point, including those needing assisted evacuation.
Answered from last-known zone under the honest-state rule: a person the platform cannot see is unaccounted, never assumed safe.
Nearest-responder dispatch
Send the closest capable person, not the loudest radio call.
Responders carry their own position, so dispatch decisions see people and places, never device IDs.
Asset tracking & search time
The pump, the trailer, the crash cart: found instead of hunted for.
The same canonical fix that locates a person locates a thing, and the platform prefers the right room to a confidently wrong dot.
Visitor & contractor
Check-in issues a tag, binds it to the person, and arms supervision from the first minute on site.
Identity-first from the kiosk onward: hosts and escorts see a name, never a MAC address.
Incident reconstruction & evidence
Replay what happened (who was where, what fired, who acknowledged) for coronial, regulatory and oversight review.
The audit trail is tamper-evident and hash-chained, with the rule version that fired recoverable from the record.
Graceful degradation & resilience
When infrastructure suffers, the platform sheds analytics before operations. Duress ingest and fan-out are never shed.
A dying feed raises one infrastructure alarm, not a per-device storm, and a source that cannot be read shows unavailable.
Lost & vulnerable person
A missing resident, a lost child, a person at risk: found from the live picture, fast and with dignity.
Staleness-gated positions mean searchers are sent to honest locations. Alerting and evidence, never covert confinement.
Enable a subset, inherit the rest
Because every theme runs on the same invariants, a deployment that starts with staff duress already carries the machinery for everything else: the same tags, the same adapters, the same escalation discipline. Adding a behaviour later is configuration, not a new procurement.
One alarm discipline
Every safety theme inherits the duress invariants: P1 at origination, closed-loop escalation, out-of-band failsafe, acknowledge once and stand down everywhere.
One evidence chain
Every theme writes to the same tamper-evident audit chain, so the reconstruction you need after an incident exists whether or not you planned for it.
One honest state
Every theme obeys the same rule: honest state over plausible state. A gap is shown as a gap. On a muster board, that rule is the difference between accounted for and assumed.
Start with your hardest theme
Bring the workflow that worries you most. If it is specification rather than in the build, we will say so before you rely on it.