It asks less over time, on a dial you control
Every approval, edit and rejection moves the confidence of the rule behind it. Each kind of action has its own autonomy level, auto, ask or never, that rises as trust builds. You can see every level and set it yourself, and one-way actions never promote themselves.
Autonomy, per kind of action
Rules view
Reply to routine ticket
AutoOn auto. Every reply is still logged and undoable
Refund under $500
Moved to auto8 unchanged approvals. Turn it back any time
Refund over $500
AskOne-way. Stays on ask until you move it yourself
Your decisions this morning
- 09:02Approved a $340 refund for Northwind
- 09:15Approved a $120 refund for Atlas Labs
- 09:31Approved a $2,400 refund for Meridian
- 09:48Approved a $480 refund for Cedar & Co
How it works
Your decisions are the training data
- 01
You decide, it records why
Each approval, edit or rejection is tied to the rule that caused the pause. Approve a $300 refund unchanged and the rule under it gains confidence. Edit the draft and it keeps the edit.
- 02
Confidence moves
Consistent approvals raise it slowly. A rejection or an edit drops it at once. One correction is enough to send a rule back to asking.
- 03
Autonomy follows trust
Each kind of action has its own level: auto, ask or never. A reversible action with a confident rule behind it moves from ask to auto, and you see it move. One-way actions stay on ask until you say otherwise.
- 04
You see the dial
Every action's level, its confidence and the decisions behind it sit in the rules view. Turn any of them down in one click or one sentence, and it takes effect on the next run.
Three levels
Auto, ask or never
Set per kind of action, not per tool or per team. Every level is visible, and you can change any of them in plain language.
Auto
It does the work, checks the result and logs it. Reversible, routine actions that fit a confident rule: replying to a routine ticket, filing a known bug, reminding on an overdue invoice.
Ask
It prepares everything and stops. You approve, edit or reject in Slack, Teams or the app. The default for anything one-way: payments, sends, deploys, deletes.
Never
It will not do this, even when a run calls for it. Deleting customer data, changing payroll. The run stops and routes the step to a person.
Off your plate
Stop approving the same thing twice
Every yes you give should count for something. With org.run it does, and you can see exactly what it counted for.
- Approving the same $40 refund for the hundredth time
- Explaining the same correction twice
- Wondering why it still asks about routine tickets
- Guessing how much the system is allowed to do
- Re-reviewing drafts you have approved unchanged for months
- Tuning thresholds by hand after every incident
- Finding out it learned the wrong lesson a month later
- Trusting a black box with your policies
The dial
Autonomy you can see, set and take back
Nothing about how it decides is hidden. Every level and every change to it has a history.
A dial per kind of action
Reply to routine ticket, refund under $500, production deploy. Each has its own level and its own confidence, not one global setting.
Confidence you can read
Every rule shows how confident it is and the approvals, edits and rejections that got it there. No number without its evidence.
One-way actions never self-promote
Payments, sends, deploys and deletes stay on ask until you move them. Consistent approvals raise confidence, not autonomy.
Edits teach, not just yes and no
Change the tone of a draft or the amount on a credit and the correction is kept, so the next draft starts where you left it.
Turn it down any time
Drop an action from auto to ask in one click or one sentence. It takes effect on the next run, and the change is logged with who made it.
Replay before you raise it
Before moving an action to auto, replay last month under the new level and see exactly what it would have done alone.
Questions about the learning loop
No. Each kind of action has its own autonomy level. Approve consistently and the rule's confidence rises. For reversible actions the level moves from ask to auto, and you see it move. For one-way actions it stays on ask until you raise it yourself.
No. Payments, external sends, deploys and deletes never move to auto on their own, however many times you have approved them. You raise those levels yourself, and you can replay last month under the new level first.
The rule behind it loses confidence immediately. One rejection or edit is enough to send an action back to asking. The edit itself is kept, so the next attempt starts from your version.
Approvals count toward the rule they belong to, and every rule has an owner and a scope. Priya's approvals on enterprise refunds move that rule; they do not touch the rule for support replies. The owner can see every decision that shaped their rule.
Yes. The rules view lists every kind of action, its level, its confidence and the decisions behind it, and you can change any of it in plain language. Nothing about how it decides is hidden.
Early access
Trust it a little more every week
Start with everything on ask and watch the dial move as it earns it.
Scoped, auditable and reversible from day one. Your data stays yours.