Atomicity means a transaction’s operations either all take effect or none do. In a cancellation flow, the database protects only the steps inside its transaction, not every real-world consequence. section 7.5
Audit atomicity by asking:
- Can a crash leave data half-written? section 7.5
- Which actions commit together, and which occur through independent network calls? section 7.5
- What happens if the process crashes after cancellation is recorded but before a refund or calendar deletion? section 7.5
- Which retries require idempotency keys to prevent duplicate effects? section 7.5


















