📄️ Action Plans (Alarm Handling)
The per-alarm-type Action Plan editor — handling dispositions (Control room, Review queue, Log & notify, Log only), the life-safety safety floor, priorities, operator instructions, and per-site-mode overrides.
📄️ Operator Checklists
The steps an operator or responder must tick off before an event can be resolved — authored inside an alarm type's Action Plan, at control-room level or per site.
📄️ Supervision & Escalation
Author a staged escalation ladder for hub-offline, open/close, expected-signal (FTT), unresolved-fault, and camera-issue (video loss) supervision — a VCR default plus per-site override. Each stage fires an action (push, Telegram, control-room event, phone-the-client task, email the client, a Service Ops note + job, a CRM ticket, management review, or silent log) after a delay — including the failed-to-test contact flow with cross-operator accountability.
📄️ Auto-complete
Configure the VCR-level policy that auto-completes (hard-closes) resolved events in Clava-Mode VCRs, with a per-site override.
📄️ Alarm Types & Groups
Name and group alarm codes, set the handling type an action plan keys off, and override how the Brain classifies them, per VCR or per site.
📄️ Alarm Receivers
Connect third-party alarm panels (Olarm, Ajax, Hyyp, Onyyx, FSK and more) to your control room — the receiver table, the Add receiver flow, and the IDS-portal vs edit-modal distinction.
📄️ Deterrence Messages
Pre-write the talk-down messages your operators play over site cameras, and see which cameras can play audio, sound a siren, or flash a red/blue strobe.
📄️ Event Burst Bounds
Two database-level bounds -- a quiet window and a detection cap -- that stop a single incident from stacking new detections indefinitely, plus the runaway-camera fault flag the cap can raise.
📄️ SOP Builder (retired)
The branching SOP flowchart prototype was retired in June 2026. Alarm handling is configured with Action Plans instead.