A Routine is the schedule and operating recipe that supports a longer Outcome Task. It is not another work item, owner, or status. Examples include a daily CEO brief, a weekly competitor reading, or a monthly retention check.
How Routines work
- Give Tycoon Agent the Outcome and cadence. She creates or reuses the root Task.
- Bind one supporting Routine. It owns the schedule and default execution recipe.
- Run on schedule. Each run is a bounded child execution or evidence lane under the Outcome.
- Read one result. Work shows the current judgment, latest evidence, next check, and any live decision. Open the Task to ask Tycoon Agent about it.
Built-in platform routines
Tycoon has platform-owned routines that ensure when you connect a supported service. Other recurring work is created when you ask for it or approve it. A routine like the calendar watcher is an example of a platform auto-owned routine that supports a meeting-watch Task.
Creating your own routines
Ask Tycoon Agent for the result and cadence. For example, "Keep our competitor positioning current; check the top three every weekday at 8am." Tycoon Agent owns the Outcome Task, selects a suitable agent for each run, and rolls material findings into the same Task. If a concrete schedule or a stopping bar is missing, Tycoon Agent pauses the Routine until the Task accepts a concrete plan.
FAQ
Q: Can I pause a routine?
A: Yes. Ask Tycoon Agent or use the Repeat controls on the Outcome. Pausing cadence does not cancel or redefine the Outcome Task. Only Routine has a resumable paused state.
Q: What happens if a run fails?
A: The error is recorded. Future runs continue normally, and failed runs can be inspected and retried. A routine run never communicates on its own; it wakes the parent Outcome Task, which decides what to report.
Q: How many routines can I have?
A: No hard limit. Each run costs credits based on the work the agent does.
Q: Can I delete platform routines?
A: Platform routines like the calendar watcher are protected by the platform and cannot be deleted, but they can be paused or stopped through the owning Task.
For how routine updates reach you, see what the Daily Update is.
See task lifecycle for how the owning Outcome Task moves through states.