Home › Scheduled AI agents with approval gates: the rule we run under
Scheduled AI agents with approval gates: the rule we run under
Affiliate disclosure: Mulkern AI Systems is an independent affiliate partner of Easy (easy.one), a product of Smart Apps Limited. If you buy Easy through our links, Mike Mulkern earns a commission, and the coupon applied at checkout (MICHAEL) is his. Everything on this page describes how we run our own businesses on Easy. It is our experience, not a statement by Easy.
Our Easy installation runs about forty scheduled jobs (counted 30 October 2026). All of them work under one rule Mike set on 28 September 2026: agents may search, read, investigate, and recommend, but nothing in his systems changes without a review and his approval. This page sets out the three tiers we use for approval gates and why we adopted them.
The three tiers
Some actions always stop and wait for Mike, one at a time: spending money, anything that reaches a real person outside the business, deleting or revoking anything, credentials, live pricing or legal copy, and service restarts.
Reversible internal repairs (configuration, documents, prompts, schedules, code fixes) are staged and reviewed, then go to Mike as one daily batch. Reading, measuring, diagnosing, testing against copies, and writing notes need no approval at all, and agents are told never to ask permission to investigate.
Three tests for every staged change
A staged change must be reversible, with the undo written down before starting. It must be traceable: what changed, when, and why. And it must be owned by one named agent, so two agents are never editing the same file.
The undo requirement does most of the work. Writing the undo first forces the agent to know exactly what it is about to change.
A narrow exception for content
Publishing would stall whenever Mike was away, so there is one standing exception. An agent may publish content (pages, posts, titles, metadata) to a property that is already live, when the exact reviewed bytes are published unchanged and an undo is recorded first.
The exception is narrow on purpose. Pricing, checkout, legal copy, anything with a live payment link, and any new product going live still wait for Mike.
How approvals work in Easy
Easy describes approvals before critical actions, alerts on a channel you choose, credentials in an encrypted vault, and usage you can see. Workflows can include approval gates and keep a log of every run.
Our rule sits on top of those parts. It lives in a short instruction file that every agent reads on every turn, which is why we keep it short.
In the Easy documentation, see Stay in control and Flows.
Questions
Does an approval rule slow everything down?
Investigation is never gated, so agents keep working. Only changes wait, and routine ones are batched into a single daily decision.
Can agents make phone calls?
Not in our setup. Phone calls to outside parties are a hard boundary with no approved form: only Mike makes calls.
Where does the rule live?
In a site-wide instruction file that every agent on the installation reads on every turn.
Is this page sponsored by Easy?
No. It is an affiliate page written by Mulkern AI Systems. Mike earns a commission on purchases made through our links.
More from how we run on Easy
Easy is the platform both of our companies run on. Our main page explains what it is, compares the three plans, and applies our coupon at checkout.
See the plans on our Easy page