Part II · Compounding harness · 11
Cron runbooks
Scheduled work as a full runbook. Each fire starts without prior session memory.
25 min
Amnesia is intentional
01
Schedule
When
02
Runbook
Full context
03
Fire
Fresh session
04
Deliver
File / TG
05
Fail path
Alert human
Cron usually runs with the always-on gateway. Each execution is an isolated session that does not inherit "yesterday’s issue." Write a self-contained runbook into the job prompt.
- Include host, path, command, expected state, delivery target, success and failure behavior.
- silent: suppress "all good" noise; still surface failures.
- no_agent / script-only: deterministic checks that need no model tokens.
- Wake gate: cheap pre-check first; wake the model only when something changed.
- Jobs must not spawn unbounded new jobs, runaway self-scheduling is blocked in healthy setups.
- Dangerous commands: prefer approvals.cron_mode deny (default) so headless jobs cannot YOLO host damage.
Build one job
Steps · tap to check0/4
Cron spend is easy to waste. Prefer script checks first; wake the model only when the check fails or changes.
Cron feature docs ↗
Automate with cron (guide) ↗
Lab: webhooks →
Sample runbook ↘
Proof
Checklist · this device0/3
Proof of completion
You created one self-contained cron job (or a complete plan) covering host, path, success, failure, and delivery, and ran it once or dry-ran the prompt.
Proof · this device0/1
Stored on this device only, not sent anywhere.