Separate optional announcements from booking operations
A single email-enabled flag suppresses booking confirmations when a member opts out of product announcements.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Domain modeling · Policy evaluation
Estimated field mix
- Privacy engineering80%
- Backend20%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Define separate purpose identifiers and allowed message categories.
- Specify defaults and unknown-purpose behavior under the fictional product policy.
- Keep preference evaluation explicit for each dispatch request.
Implementation constraints
- Do not infer a legal basis from a message label; the exercise uses a declared product rule.
Verification to include
- Evaluate announcement and booking fixtures with optional announcements disabled.
- Reject an unknown purpose instead of silently treating it as operational.
Deliverables
- Purpose registry and preference truth table
Rollout and recovery
Introduce purpose tags before migrating existing preference checks.
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.