Approval gates are a feature, not a limitation

Every automation vendor promises hands-off. Every operator who has been burned knows the real question: what happens at the edge cases?

Turbine ships with approval gates on every flow. Refunds above your limit, sends above your volume, any action the policy calls ambiguous — the run stops, packages its plan and evidence, and asks.

Autonomy is granted in increments, and the gate is where it is earned.

Asking is designed to be cheap: approve from Slack in one tap, edit the draft inline, or take the task over entirely. The run logs whichever you choose.

Teams loosen the gates themselves, per task and per amount, as the audit log builds their confidence. Week one is gates-everywhere; by week six, refunds under $250 just run.

That progression — earned, visible, reversible — is the product. Hands-off is the result, never the promise.