Write the compensation table for return side effects
The team calls every reverse action rollback, although an issued label can be voided and a completed inspection cannot be undone.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Compensation design · Tradeoff analysis
Estimated field mix
- Distributed systems60%
- System design40%
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
- Classify compensatable, irreversible and unresolved effects.
- State preconditions and outcomes for each compensation.
- Separate corrective actions from deletion of historical facts.
Implementation constraints
- Use fake providers and document their exact capabilities.
Verification to include
- Map a voidable unused label to its compensation.
- Map completed inspection to retained history rather than pretending it can be erased.
Deliverables
- Compensation decision table
Rollout and recovery
Review provider capabilities before orchestrator work; block unsupported automatic reversals.
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.