Recheck optional-message eligibility immediately before provider dispatch
An audience list was built yesterday. A member who opted out this morning still receives the queued announcement.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Authorization timing · Queue processing
Estimated field mix
- Privacy engineering50%
- Security30%
- Platform engineering20%
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 event workspace offers optional product announcements and operational booking messages. Its product policy treats these as separate purposes. A stale audience cache currently sends optional messages after a member opts out. The brief implements fictional preference rules and makes no legal-consent certification.
Setup prerequisites
- Create synthetic members, versioned notice text and two purpose-tagged message types.
- Use a fake dispatch provider with controllable queueing and acknowledgement; send no real messages.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Evaluate current purpose-specific preference at the dispatch boundary.
- Suppress ineligible work with a recorded safe reason and no provider call.
- Define behavior when preference state is unavailable; optional delivery must not assume permission from a stale list.
Implementation constraints
- The audience snapshot is planning input, not final dispatch authority.
Verification to include
- Queue while enabled, opt out, then release the job and verify no provider request.
- Make the preference repository unavailable and verify the declared hold/suppression path without sending.
Deliverables
- Dispatch guard and stale-audience regressions
Rollout and recovery
Deploy the guard before replaying old queue entries; monitor bounded suppression categories.
Value of the work
For the engineer: Practice purpose modeling, versioned user choices, dispatch-time checks and consistency under retries.
For the team: Create an inspectable preference workflow that can be reviewed against a company-approved communication policy.
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.