Exercise preference revocation during a notification backlog
A user disables a channel while thousands of queued intents wait for provider quota, exposing ambiguous preference timing.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Policy consistency · Fault scenarios
Estimated field mix
- System design40%
- Privacy engineering30%
- Quality engineering30%
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
- ANOTIFY-108 · Calculate notification drain time under a channel rate limit
Acceptance criteria
- Apply the chosen preference-timing policy consistently.
- Record suppressed versus attempted outcomes without contact details.
- Keep already accepted provider facts immutable.
Implementation constraints
- Use a local backlog and fake provider; send no real messages.
Verification to include
- Change preferences before a queued intent reaches its decision boundary.
- Change preferences after provider acceptance and preserve the accepted fact without claiming recall.
Deliverables
- Backlog preference drill and outcome trace
Rollout and recovery
Run before adapter approval; suspend the affected category if policy and implementation diverge.
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.