When a hard stop resolves to escalation, a named human is alerted and the ladder starts. Acknowledgment, SLA breach, fallback and the operator alarm are separate states — all four are shown here.
DEMO · SYNTHETIC DATAThis console is a public product tour served from synthetic fixtures. There is no login, no tenant credential in the page, and no connection to a Regent backend. A real tenant console requires a server-side session boundary before a browser may reach tenant-scoped APIs.
When a crisis flag is present in the accepted request context, the pre-agent hard stop resolves the escalation before the judgment engine is invoked. No outreach is proposed, none is sent, and the named escalation path executes. Non-overridable at decision time. There is no operator bypass.
UHC-PT-00217
Crisis flag present in the accepted snapshot · pre-agent hard stop
Acknowledged
Named target
Dr. Nour Khalil · on-call clinical lead
Raised
18 Aug 2026 · 16:47:22 UTC
Acknowledgment SLA
15 minutes
Acknowledged
16:52:40 UTC
✓
Alert delivered to primary target — done16:47:22 UTC
WhatsApp alert to the on-call clinical lead, backed by a durable alarm row.
✓
Acknowledged in dashboard — done16:52:40 UTC
Acknowledged 5m 18s into a 15-minute SLA. The ladder stops here.
·
Fallback target — pending
Not reached — the primary target acknowledged inside the SLA.
Crisis flag present in the accepted snapshot · pre-agent hard stop
Operator alarm raised
Named target
Dr. Nour Khalil · on-call clinical lead
Raised
16 Aug 2026 · 03:04:12 UTC
Acknowledgment SLA
15 minutes
Acknowledged
not yet
✓
Alert delivered to primary target — done03:04:12 UTC
No acknowledgment inside the SLA.
✕
Acknowledged in dashboard — failed03:19:12 UTC
SLA expired.
✕
Fallback target — failed03:34:13 UTC
Clinical duty desk did not acknowledge inside its own SLA.
◍
Operator alarm — active03:34:14 UTC
Named operator alarm raised: Sentry alert on the wired project plus a WhatsApp message to the named operator, backed by a durable alarm row that retries until acknowledged.
Disabled in the demo. This action belongs to a signed backend sprint. The ladder above is synthetic: it is rendered from fixtures so you can read every state the chain can reach. Acknowledgment writes to the durable alarm row, which belongs to the escalation chain the end-to-end go-live checklist builds and exercises. That chain is not deployed yet, so nothing here alerts a real person.