Keep one persistent notification visible across web and mobile even when a push is missed.
Track
Notification Follow-through
Phase
Inbox lifecycle
Starts with
Unread persistent notification
Ends with
Read, completed, or archived notification with preserved history
A supported domain event creates one recipient-specific inbox record. The user can read, reopen, complete when action is required, or archive it while delivery history remains auditable.
A supported event creates a persistent notification for the signed-in user.
Builds the cross-lodge picture, routes action, and retains follow-up.
Confirms priority, ownership, acceptance, or closure when required.
Cross-scope readiness signals linked to their trusted source context.
Why: Find the exact work that needs attention without copying its ownership.
The priority, named owner, accepted handoff, or closure evidence.
Why: Make the operating decision with explicit accountability.
The Inbox preserves notification lifecycle; push is only a delivery channel and the source workflow remains authoritative.