Safety & escalation
Five seconds, five beats.
When the rule fires, three parallel surfaces light up: the patient sees one-tap crisis routes, your caseload pings with pre-loaded context, and the audit log takes an immutable entry. None of this depends on model judgment.
The film
25 seconds, as it happens.
Storyboard
Every beat, frame by frame.
Motion-free read of the same path. Also the fallback when a reader has prefers-reduced-motion set.
- 01
The patient types a message that matches a risk pattern.
“I don’t think I can keep doing this.”T+0s - 02
A rule-based detector fires. Not the model.
Rule firedSAFE-T tier change detected · deterministic path engagedT+2s - 03
Three one-tap routes surface in session.
Call 988Text HOME · 741741Call Dr. ChenT+3s - 04
The supervising clinician’s caseload pings.
Jordan K.T+4s - 05
The event lands in the immutable audit log.
ESCALATION 2026-04-23T14:52:17Z · rule: CSSRS-tier-up · routed: patient + 988 + 741741 + clinicianT+5s
The flow
Signal · rule · three parallel actions.
Signal
Patient message matches risk pattern
C-SSRS tier change · SAFE-T criteria · imminent-risk lexicon
T+0s
Rule fires
Deterministic detector
Not the model. A rule-based classifier against a fixed ontology. Auditable line by line.
T+2s
In-sessionT+3s
Crisis routes surface as one-tap actions
- Call 988
- Text HOME to 741741
- Call Dr. Chen
ClinicianT+4s
Supervising clinician ping
- Caseload row pulses sapphire
- SMS + in-app alert
- Patient context pre-loaded
AuditT+5s
Immutable log entry
- Rule ID · severity tier
- Timestamp · patient hash
- Included in monthly telemetry
Go deeper
The full safety architecture is in the model card.
The six-layer evaluation that gates every release, ten named failure modes we test for, and the dependency-design commitments that shape what the companion will and will not do.