When should you avoid a fancy use of transactions?
How does transactions affect maintainability?
What state reasoning matters with transactions?
What naming guidance fits transactions?
What boundary guidance fits transactions?
What data-shape guidance fits transactions?
What failure handling lens fits transactions?
What performance guidance fits transactions?
What is the best default for transactions?
Why does OrderOps care about transactions?