Part 2 · Set up
Autonomy stages
How much runs without you. Four stages, and none removes your approval on a message.
01What it is
A setting on your workspace that decides how much the system does on its own. It is database state and every check reads it server-side.
02Why it exists
Autonomy is earned by evidence rather than granted by preference. The reason to move up a stage is that you stopped editing drafts, and the reason to move down is that you started again.
No stage removes your approval on a message to a named person. Higher stages widen what the system decides on its own: which experiment gets budget, when a follow-up goes, what gets tried next.
03How to use it
- 01Start at You approve everything. It drafts and you approve every send.
- 02Move to Your rules approve routine work once you approve most drafts without editing.
- 03Use the global pause rather than dropping a stage when something looks wrong. It takes effect at every stage immediately.
- 04Check your plan. The later settings need a bigger plan and the gate enforces it.
04What good looks like
- You give it
- Two weeks at You approve everything with a falling edit rate, then a move to Your rules approve routine work.
- You get
- Routine sends go inside the limits you set, and exceptions still come to you.
- Why
- Your rules approve routine work sends within limits and surfaces anything below the confidence bar.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- It tests inside your limits, on day one.
- You get
- The gate refuses. The stage is capped by your plan, and the drafts still need approval that nobody has read.
- Why
- The pre-send gate checks the stage against the plan and refuses with a named reason.
Derived from the rules in the code