Event-Driven Notification Platform · View 14 of 26 · 4 · Runtime

Notification Orchestration

The seven questions asked of every event, in order, and what happens when the answer is no.

Editable source SVG draw.io All views

Decisions

Should notify, who, what, which channel, when, guardrails, dispatch — evaluated in that order because each stage narrows the next
Preference is checked before rendering, so an opted-out recipient never costs a render
Deduplication sits after the timing decision so that a delayed and an immediate copy of the same intent collapse

Suppression is not silence

Every suppression increments a labelled counter and writes a reason on the notification record
A notification that was never sent is still a notification with an answer — this is what makes the support question answerable
Suppression reasons: no rule, opted out, duplicate, over cap, quiet hours, tenant paused

Assumption

Rules are declarative CEL, not arbitrary code, so a tenant rule is sandboxed and its cost is bounded
If rules genuinely need arbitrary logic, that is a webhook callout and a different design; confirm before build

◀ Preference, Consent and Override Policy All views Event to Delivered Email ▶