Automation Proof Contract

A scheduled thread is not a completed automation until it leaves output, state, log, and any promoted wiki changes behind.

Schedulers can create activity without durable memory. The proof contract prevents that. A run matters only when future agents can inspect what happened and when freshness can see the result. Source: Scheduling Operating Model; automations/_schema.md

Required Artifacts

Completion Checklist

1. Read the canonical automation markdown.
2. Gather only permitted sources.
3. Write the output artifact before or alongside durable edits.
4. Decide promotion vs no durable update.
5. Update the correct state.json keys.
6. Append wiki/log.md.
7. Rebuild index/qmd and run targeted checks when pages, skills, routing, or config changed.

State Discipline

For sub-daily jobs, use ISO timestamps. Date-only values hide hour-level drift. For integration syncs, update syncs.* only after successful collection. A blocker report may update automations.<slug>, but it must not pretend the external source synced.

---

Timeline

• 2026-07-01 | Created as the explicit durable proof contract for scheduled automation runs. Source: User request, 2026-07-01; automations/_schema.md; scheduling-operating-model