Notification request processing and settlement

The Lifecycle

Transitions Explained

The transition rows describe stored state changes, their checks and their recorded effects. A queue receive, provider outcome and staff action can reach different lifecycle boundaries.

What Cannot Happen

A settled request is excluded from withdrawal. An existing non-accepted outcome prevents another acceptance attempt. Correcting rejected input requires another publication. Repeated queue work resumes dispatch rather than removing the existing outcome.

Concurrency and Timing

The derived request identity prevents duplicate outcomes. Conditional settlement coordinates withdrawal with reconciliation. An early cancellation persists as a tombstone that later publication checks, so processing does not require queue order.