Specify recipient resolution without copying event payloads broadly
The event producer includes every collaborator's contact details so downstream handlers can decide recipients.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Privacy boundaries · Authorization
Estimated field mix
- Privacy engineering50%
- System design30%
- Security20%
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 collaboration tool sends email and in-app notifications. Duplicate alerts and preference changes reveal that the design has no single definition of delivery.
Setup prerequisites
- Create synthetic recipients, events and fake delivery providers.
- Do not send real email or messages.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Resolve recipients through a scoped authority boundary.
- Keep generic event payloads to opaque identifiers.
- Authorize recipient access before creating a channel attempt.
Implementation constraints
- Use synthetic addresses and a dedicated contact provider fake.
Verification to include
- Resolve members of the correct synthetic workspace.
- Request recipients across workspaces and produce no channel attempts.
Deliverables
- Recipient-resolution contract
Rollout and recovery
Review the contract before broad event publication; quarantine events without valid scope.
Value of the work
For the engineer: Practice asynchronous contracts, preference timing and delivery uncertainty.
For the team: Review a notification design that controls nuisance, disclosure and recovery.
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.