What a routine is
A routine is work the colony runs on a schedule without you starting it: a Monday planning pass, a nightly digest, a Friday update. A good routine has a trigger (when it runs), a job (the work), and an output (what shows up when it finishes). If a routine produces nothing you ever look at, it should not exist.
Routines respect every control
A scheduled job still hits your approval gates, still counts against your budget, and still appears in the audit trail. A routine cannot do anything an agent could not do in a live conversation; it just does it on a clock. You can trust a routine exactly as much as you trust the agent that runs it.
Start with one
The best first routine is a morning brief: every weekday, the CEO compiles what happened overnight, what is waiting on approval, where spend stands, and the plan for the day. Add a second routine only when the first earns it, and review your routines monthly so the calendar does not fill with jobs you ignore.
The arc of a good routine
A routine usually starts as reporting: it tells you what happened. As you come to trust it, you let it recommend: the morning brief stops just summarizing and starts proposing the obvious next actions. Eventually, within your gates, it can act: queuing those actions for a single tap of approval. That progression, from reporting to recommending to acting, is the whole arc of running an AI-native business, and routines are where you watch it unfold.
You control the pace. A routine only ever does what the agent behind it is allowed to do, so moving it from reporting toward acting is a decision you make as your confidence grows, not something that happens on its own.
Avoiding routine drift
A routine that made sense in month one can quietly become noise by month three, either because the business changed or because it never delivered. The fix is a monthly review: list every routine, when it runs, and the last time its output mattered. Keep the ones you read, fix the ones that are close, and retire the ones you skip. A small set of routines you rely on beats a calendar full of jobs you ignore.
This article is part of the launch docs set; boundaries and depth are still being reviewed with engineering and will keep sharpening.
