Bind a queued announcement to its purpose and content revision
An operator edits a queued campaign from a booking reminder into promotional content while retaining the original operational tag.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Immutable inputs · Purpose limitation
Estimated field mix
- Privacy engineering60%
- Data engineering40%
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
- Freeze purpose and content revision for each queued delivery request.
- Require a new reviewed request when a material content/purpose change occurs.
- Reject dispatch when the referenced purpose or content revision cannot be resolved.
Implementation constraints
- Use synthetic content and a local review state; this ticket sends nothing outside the provider double.
Verification to include
- Edit the source campaign after queueing and verify the queued revision remains identifiable.
- Attempt to retag optional content as operational through a mutable field and verify the request is rejected.
Deliverables
- Immutable dispatch request contract and revision tests
Rollout and recovery
Version the queue payload and hold unresolved legacy jobs for explicit conversion.
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.