Notification Rules
Every channel declares the lowest severity it will carry — its threshold. A notification is delivered on a channel when its severity sits at or above that threshold, so the matrix below is derived directly from the policy and can never drift. Quiet hours then override the matrix overnight, holding low-severity traffic and keeping only the pager paths live.
Routing Matrix
Channel × severity. A filled cell means a notification of that severity is delivered on that channel under the normal (active) policy.
| Channel | Threshold | Info | Warning | Critical |
|---|---|---|---|---|
Daily digestdigest Rolled-up email summary delivered once per shift handover. | ≥ Info | |||
Ops chat#ops Shared operations channel; the room most people watch. | ≥ Warning | — | ||
Owner emailmail Direct email to the item owner and their area lead. | ≥ Warning | — | ||
On-call pagerPD Phone-waking page to the on-call commander. | ≥ Critical | — | — |
Cells are computed from each channel's threshold, not hand-edited — raise a threshold and its row simply loses the lower-severity cells.
Quiet Hours
Outside the window everything is held except pager paths, and even those only fire at or above the quiet-hours floor.
Window
22:00 – 07:00 (Event-local)
Pages at or above
Held traffic
Held and rolled into the next daily digest at the end of the window.
Reachability Check
For each severity, which channels light up under the normal policy — a quick read on whether anything could go unnoticed.
- Daily digest
- Daily digest
- Ops chat
- Owner email
- Daily digest
- Ops chat
- Owner email
- On-call pager
Notification rules are illustrative cockpit project-tracking state authored in src/data/notification-rules, not product data. The matrix and quiet-hours behavior are both derived from the channel thresholds.