Separate notification intent from channel delivery and human receipt
Product labels a notification delivered when an email provider accepts it, though no human receipt is observed.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Domain modeling · Delivery semantics
Estimated field mix
- System design60%
- Backend40%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Define intent, attempted, provider-accepted and observed-read states.
- Keep channel-specific facts separate.
- Avoid claiming reading from provider acceptance.
Implementation constraints
- Use synthetic provider receipts and explicit unknown states.
Verification to include
- Map an accepted email and an opened in-app item separately.
- Timeout the provider and retain unknown delivery rather than sent.
Deliverables
- Notification semantics table
Rollout and recovery
Adopt precise status labels in the prototype; preserve uncertain older observations.
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.