Scheduled agent work should not outlive the operator session. JARVIS agents run recurring jobs in tmux pane 2 — beside the Rocket.Chat monitor — so when the session is killed, routines stop with it. No orphaned cron on a laptop, no silent jobs on a forgotten VM.
Pattern
A routine script loops: do one job, post a summary to the agent channel, sleep. Output appends to logs/routines.log. Startup rows in context.md document which routines should be running so a fresh boot does not double-launch.
What we want next
- Workflow templates: deploy check, inbox sweep, disk alert — promoted from utilities to routines.
- Cross-step playbooks where one human message kicks a documented multi-step flow.
- Blog posts here when a workflow graduates from experiment to default.
The harness stays the same; workflows are how execution compounds without losing supervision.