Read models
Event and channel pairs with both halves a notification needs.
Event and channel pairs with both halves a notification needs.
Beside them, what actually reached somebody. Either half alone sends nothing.
Superseded on screen by api.notification_events, which answers the same question one level up — per event rather than per pairing, and over every event the product can raise rather than only the ones a tenant has configured. Kept because the api schema is the public interface and a read model somebody integrates against is not ours to withdraw for being unfashionable; there is no screen behind it any more.

