Notifications

Notification intent is distinct from provider delivery. Routing selects an eligible endpoint; delivery records provider attempts, outcomes, retry state, and feedback without rewriting the incident lifecycle.

The control plane stores one logical intent and provider-specific attempts. Stable identity makes retries safe, while provider admission protects shared capacity. Retryable, permanent, deferred, and successful outcomes have different operator actions; a queued intent is not proof that a human received it.

Endpoint verification, user preferences, service routing, provider configuration, and incident urgency all participate in eligibility. Provider callbacks update delivery evidence but cannot move the incident lifecycle. See the delivery reference and inspection guide.