Reconcile audience caches without restoring old optional choices
A nightly audience rebuild copies an old export over the current preference cache.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Cache reconciliation · Conflict handling
Estimated field mix
- Distributed systems40%
- Privacy engineering40%
- Data 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.
- RCONSENT-101 · Separate optional announcements from booking operations
- RCONSENT-102 · Record the notice version shown when a preference changes
- RCONSENT-104 · Recheck optional-message eligibility immediately before provider dispatch
- RCONSENT-106 · Stop an opt-out retry from being lost behind an older opt-in event
Acceptance criteria
- Bind rebuild inputs to a declared cutoff and subject/purpose revisions.
- Prevent rebuild writes from replacing newer authoritative or replicated choices.
- Report missing and contradictory inputs as reconciliation exceptions.
Implementation constraints
- Treat audience caches as derived state; preserve current choice authority outside the rebuild.
Verification to include
- Run a rebuild while a member opts out and verify the newer revision wins.
- Feed contradictory same-revision values and verify the rebuild stops or quarantines them without guessing.
Deliverables
- Audience reconciliation and concurrent-choice tests
Rollout and recovery
Build into a new cache generation and switch only after consistency checks; retain the prior generation for diagnosis.
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.