Define stable provider command keys for each return step
A retry after a lost response creates a second shipping label because each request receives a new key.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Idempotency · Provider contracts
Estimated field mix
- Distributed systems60%
- Integrations40%
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 equipment-rental service approves returns through several provider calls. Partial failures leave labels issued without inspections or refunds reported before provider confirmation.
Setup prerequisites
- Create synthetic return records and fake inspection, shipping and refund adapters.
- Use integer money values and no real payments or messages.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Bind keys to return identity, step and generation.
- Reuse keys for equivalent retries.
- Reject changed canonical input under an existing key.
Implementation constraints
- Do not reuse one key across unrelated provider actions.
Verification to include
- Repeat a label request and resolve one fake provider result.
- Change shipping destination under the same key and return conflict.
Deliverables
- Step identity contract and provider-key tests
Rollout and recovery
Use stable keys before enabling retries; reconcile legacy ambiguous effects separately.
Value of the work
For the engineer: Practice durable workflow state, compensation and uncertain outcomes.
For the team: Review recoverable business operations without assuming distributed transactions.
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.