Keep in-app notification reads separate from email provider state
Marking an in-app alert read currently suppresses an unrelated email retry by changing one shared status column.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- State separation · Authorization
Estimated field mix
- System design50%
- Backend50%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional collaboration tool sends email and in-app notifications. Duplicate alerts and preference changes reveal that the design has no single definition of delivery.
Setup prerequisites
- Create synthetic recipients, events and fake delivery providers.
- Do not send real email or messages.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- ANOTIFY-101 · Separate notification intent from channel delivery and human receipt
- ANOTIFY-102 · Specify recipient resolution without copying event payloads broadly
- ANOTIFY-103 · Choose when notification preferences are evaluated
- ANOTIFY-104 · Model notification intent and dispatch in one durable transaction
- ANOTIFY-105 · Design per-channel attempt identity and provider reconciliation
- ANOTIFY-106 · Bound notification fan-out without creating one huge transaction
Acceptance criteria
- Model channel delivery and in-app acknowledgement separately.
- Bind acknowledgement to the authenticated recipient.
- Preserve delivery-attempt history after acknowledgement.
Implementation constraints
- Use an explicit read model for the in-app feed.
Verification to include
- Mark one in-app item read and retain email attempt state.
- Acknowledge another recipient's item and reject it.
Deliverables
- Read-model contract and channel-isolation probe
Rollout and recovery
Prototype the read model behind a local route; revert read wiring without changing delivery history.
Value of the work
For the engineer: Practice asynchronous contracts, preference timing and delivery uncertainty.
For the team: Review a notification design that controls nuisance, disclosure and recovery.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.