12.0Workflows
The work that starts without anyone asking
A schedule or a connected event gives an agent recurring work. Each watcher pauses on its own, so narrowing what runs never means stopping the whole workforce.
Triggers
7 watching · 1 paused
- Stock cover sweepScheduleEvery day, 06:00 · Atlas · today 06:00 · 14 lines checked, 2 held
- Order exceptionEventOn a failed fulfilment · Atlas · 11 min ago · 1 raised
- Unanswered for 4 hoursScheduleHourly · Mira · 24 min ago · nothing waiting
- Listing quality checkScheduleMondays, 08:00 · Mira · paused 3 days agoPaused after the connection was revoked
- Returns older than 14 daysScheduleEvery day, 07:30 · Mira · today 07:30 · 3 chased
- Supplier confirmed a dateEventOn an inbound supplier reply · Atlas · 2 hours ago · SUP-118 updated
- Card payment declinedEventOn a failed charge · Mira · yesterday 16:11 · 1 held
- Monday briefScheduleMondays, 07:00 · Atlas · Mon 07:00 · sent to 3 people
Pausing a trigger stops that watcher only. The other 7 keep running, and anything already in flight finishes.
Pause any one of them. The count changes, the others carry on — there is no single switch that stops the whole workforce by accident.
7 watching, 1 paused.Triggered and manually started runs follow the same approval rules, permission set and credit accounting.
Triggers
Work that starts without anyone asking
Everywhere else in the product, work begins because something arrived. Here it begins because a clock or a connected event said so — a six o'clock stock sweep, an order exception the moment fulfilment fails.
Triggers
7 watching · 1 paused
- Stock cover sweepScheduleEvery day, 06:00 · Atlas · today 06:00 · 14 lines checked, 2 held
- Order exceptionEventOn a failed fulfilment · Atlas · 11 min ago · 1 raised
- Unanswered for 4 hoursScheduleHourly · Mira · 24 min ago · nothing waiting
- Listing quality checkScheduleMondays, 08:00 · Mira · paused 3 days agoPaused after the connection was revoked
- Returns older than 14 daysScheduleEvery day, 07:30 · Mira · today 07:30 · 3 chased
- Supplier confirmed a dateEventOn an inbound supplier reply · Atlas · 2 hours ago · SUP-118 updated
- Card payment declinedEventOn a failed charge · Mira · yesterday 16:11 · 1 held
- Monday briefScheduleMondays, 07:00 · Atlas · Mon 07:00 · sent to 3 people
Pausing a trigger stops that watcher only. The other 7 keep running, and anything already in flight finishes.
Pause any one of them. The count changes, the others carry on — there is no single switch that stops the whole workforce by accident.
7 watching, 1 paused.- 12.1Clocks and eventsA schedule runs in the workspace's own timezone. An event fires on something a connection reports. Both produce an ordinary run with one responsible agent.
- 12.2One switch eachEvery trigger pauses on its own. Stopping the Monday listing check leaves the six o'clock sweep running, and anything already in flight finishes.
- 12.3Auto-pause on a broken connectionA trigger whose connection is revoked pauses itself and says why, instead of failing every hour until somebody notices.
- 12.4Missed runs stay visibleA schedule that could not run is recorded as missed. Resuming continues from the next scheduled time.
Who it runs as
Every trigger names an agent
Every triggered run names a responsible agent and runs under that agent's permissions. Nothing executes as the schedule itself, so a trigger cannot be used to reach past what its agent is allowed to do.
- 12.5Permissions are the agent'sAutomatic runs use the same permission set as every other run by that agent.
- 12.6Approvals still applyA triggered run that reaches a held action waits like any other. An unattended trigger does not mean unattended spending.
- 12.7One run historyTriggered runs land in the same activity trail as work started by a person or by an arriving message, with the trigger recorded as the cause.
- 12.8Failures sit on the triggerA run that errors carries its code on the trigger itself, so the reason is on the thing you would go and look at.
The rest of the system
- 1.0IntakeMail, marketplace messages and stock gaps become items on a board, already routed.
- 2.0WatchCover counted against what is selling, so a line that runs out is flagged early.
- 3.0ActNamed agents work the item and hand it between themselves with the evidence attached.
- 4.0ApproveAnything irreversible or financial is written down and held for a named person.
- 5.0MonitorWhat moved, what is stuck, and what is waiting on you — with the numbers behind it.
- 8.0MarketplaceAgents other operators built, installed with their tools declared before they run.
- 9.0LimitsA ceiling on what runs unattended, and the actions no ceiling ever covers.
- 10.0BoardsOne board held by people and agents alike, where the column follows the owner.
- 11.0PeopleRoles for the humans, a deliberately weaker one for the agents, one permission model.
Start with one agent and one job.