Explain which queued messages an opt-out can still prevent
The settings page promises instant cancellation even when the provider has already accepted a message that cannot be recalled.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- State semantics · Product communication
Estimated field mix
- Privacy engineering60%
- Integrations40%
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.
- RCONSENT-101 · Separate optional announcements from booking operations
- RCONSENT-102 · Record the notice version shown when a preference changes
- RCONSENT-103 · Make the preference form submit the user’s explicit final choice
- RCONSENT-104 · Recheck optional-message eligibility immediately before provider dispatch
- RCONSENT-105 · Bind a queued announcement to its purpose and content revision
Acceptance criteria
- Define queued, dispatching, provider-accepted and completed boundaries.
- Describe prevention guarantees in user-facing copy consistent with those states.
- Cancel controllable work and report when a provider-accepted message is beyond the supported recall boundary.
Implementation constraints
- Do not claim that recording a preference change reverses an already completed delivery.
Verification to include
- Opt out at each controlled boundary and compare provider calls with displayed status.
- Simulate a provider without recall support and verify the interface does not show a false cancellation success.
Deliverables
- Cancellation state contract and truthful settings copy
Rollout and recovery
Publish the clarified contract with the dispatch guard; preserve accepted-delivery history under the declared retention policy.
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.