Replay workshop hold requests with the same idempotency key
Timeout retry creates two holds for one user's click. Bind the operation key to the normalized request.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Idempotency · Transactions
Estimated field mix
- Backend50%
- Database engineering30%
- API design20%
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
Fictional craft studio Maple offers workshop seats. Implement synthetic reservations without payments or real booking services.
Setup prerequisites
- Create synthetic workshops with small capacities.
- Implement local transactional hold storage and injected clocks.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Same key and payload returns same hold
- Different payload conflicts
- Keys remain scoped to owner
Implementation constraints
- Store idempotency result with the hold transaction.
Verification to include
- Replay accepted request
- Reuse key with different quantity
Deliverables
- Idempotent create contract
Rollout and recovery
Require status lookup while replay support is repaired.
Value of the work
For the engineer: Practice contention, expiry and truthful realtime projections.
For the team: Inspect whether concurrent clients avoid overselling and recover uncertain results.
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.