Work
Routines
Repeatable playbooks — define a piece of work once, run it on demand with the same controls every time.
A Routine is a piece of work you’ve defined once and can run again: “weekly vendor price check”, “prep the Monday standup brief”, “triage the support inbox”. Think playbook, not workflow diagram — you describe the outcome and constraints in plain language, and each run executes as a normal task.
Why routines instead of re-typing the request
Section titled “Why routines instead of re-typing the request”- Consistency — the same instructions, tools, and output shape every run.
- Accumulated judgment — corrections you make to one run carry forward; the routine plus your memory gets sharper over time.
- Controls included — every run is a full execution session with approvals, pauses, and the Cockpit. A routine never earns the right to skip an approval just because it ran fine last week.
Creating one
Section titled “Creating one”Define a routine from scratch, or — more commonly — from a task that went well: “save this as a routine”. Name it, state the outcome, keep the constraints that mattered (“always ask before contacting anyone external”).
Running one
Section titled “Running one”Run on demand from Routines, or attach a Schedule so it runs without you. Each run appears in Tasks like any other work, linked back to the routine it came from.
For teams
Section titled “For teams”Team routines are shared playbooks: one definition, run by anyone with access. Combined with team memory, this is how a team’s way of doing something stops living in one person’s head.