1 min read
Automation Overdue
An overdue automation is a routing signal. Decide whether to run, repair, defer, or retire it.
Freshness marks an automation overdue when the last durable run in state.json is older than the schedule, missing, or inconsistent with the configured automation. Source: scripts/check-freshness.ts; Automation Schema
Response Matrix
| Situation | Correct action |
|---|---|
| Manual/local job is overdue and in scope | Read automations/<slug>.md, run it, write output, update state/log, and validate. |
| Job requires missing credentials | Report the missing credential/session and leave the sync stale. |
| Cloud job has no local run record | Treat as notice unless local state is expected. |
| Automation is obsolete | Propose deletion, deferral, or schedule change; do not let it stay never-run forever. |
| Scheduler prompt drifted | Update live scheduler prompt to read the canonical automation file. |
Manual Run Contract
- Read
automations/_schema.md. - Read
automations/<slug>.md. - Execute only permitted sources and side effects.
- Write
outputs/<date>/<slug>/<agent>.md. - Apply wiki targets only when promotion criteria pass.
- Update
state.jsonandwiki/log.md. - Run generated-surface checks if durable pages changed.
Current Priority Classes
As of 2026-07-01, overdue work clusters into sub-daily ingest, communications/calendar syncs, daily radar/career/content jobs, weekly research/recruiting/license jobs, and self-heal. Run the current freshness check before selecting exact work. Source: npx tsx scripts/check-freshness.ts, 2026-07-01
Timeline
- 2026-07-01 | Expanded overdue handling into a run/repair/defer/retire matrix tied to durable automation proof. Source: User request, 2026-07-01
- 2026-05-31 | Automation overdue handling from session startup rules. Source: public wiki expansion, 2026-05-31