Decouple confirmation delivery from accepted registration
A slow notification provider makes accepted registrations appear failed.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Outbox · Resilience
Estimated field mix
- Distributed systems40%
- Backend40%
- Site reliability20%
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 course platform expects a registration deadline spike. Capacity assumptions, escalation ownership, and degradation decisions are scattered across old documents.
Setup prerequisites
- Create synthetic registration traces and local dependency doubles with finite connection and request limits.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Commit registration and notification intent atomically.
- Return accepted registration independently of delivery latency.
- Expose pending delivery without duplicate enrollment.
Implementation constraints
- Use a local notification double; send no messages.
Verification to include
- Accept registration during a notification outage.
- Recover delivery and verify one logical notification operation.
Deliverables
- Notification outbox flow.
Rollout and recovery
Retain pending intents through rollback; pause dispatch independently.
Value of the work
For the engineer: Practice readiness reviews, capacity reasoning, and cross-functional operational handoffs.
For the team: Produce a concrete launch-readiness assessment with measurable risks and recovery actions.
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.