Build the gate as a switch you can flip

When I build the gate in front of an irreversible action, I do not hardcode it as "always ask a human." I build it as a switch with two positions: draft-only and auto-send. Same code path, one flag. That switch is how a system climbs the autonomy ladder without a rewrite.

In draft-only, the workflow does all its work and stops at the gate, handing the finished action to me for approval. In auto-send, the exact same workflow runs straight through and takes the action itself. The only difference is the position of one flag. I start every consequential automation in draft-only, and I flip it to auto-send only when it has produced enough good output that I trust it unwatched.

Why make it a switch instead of just picking one behavior?

Because the right behavior changes over time, and you do not want a code change every time your trust does. On day one you have no evidence the automation is good, so it sits in draft-only and you are the gate. After fifty clean drafts, forcing yourself to approve the fifty-first is just friction with no safety left in it. The switch lets trust and behavior move together: promote by flipping a flag, and if the thing starts drifting, demote by flipping it back. No rebuild, no risk of breaking the workflow to change its autonomy.

My weekly newsletter drafter is built on this switch. Right now it is draft-only: it writes the wrap-up, and it waits. The plan is to promote it to auto-send once it has earned it, and when that day comes the change is one flag, not a project. The workflow that produces the email is identical in both modes. I am only moving where the stop happens.

The design rule underneath is that autonomy should be a configuration, not a foundation. If flipping your automation from supervised to unsupervised requires touching the logic, you built it wrong, because you will avoid the change and either stay slow forever or rip the gate out entirely. A clean switch keeps the safe default one decision away from the fast one, in both directions.

The takeaway: Build the gate as a draft-only to auto-send switch on the same code. Promotion becomes a flag you flip when trust is earned, and demotion is the same flag flipped back, with no rewrite either way.