Reference

`platform.schedule`

domain: platform

A SCHEDULE — the clock-driven trigger, the third way to run a component alongside manual (a person) and event (platform.subscription). Domain-agnostic, tenant-owned config (a Studio/Components app edits it): a cron expression + the component to run. A generic scheduler service ticks, finds due schedules, and fires the SAME confined run path a manual or event trigger uses (kernel run-token → host → broker). The scheduler stamps last_run/next_run/last_status back onto the record. 'Run the terrain driver nightly at 02:00' is one schedule record, not code.

Field	Type	Required	Description
`schema`	`—`	✓
`id`	`string`	✓
`name`	`string`
`tenant`	`string`		the tenant that owns this schedule (its steward prefix)
`component`	`string`	✓	component_id to run (must be installed in this tenant)
`cron`	`string`	✓	5-field cron: 'min hour dom mon dow' — supports , /n, a,b lists, a-b ranges. e.g. '0 2 * * *' = daily 02:00
`tz`	`string`		IANA timezone the cron is evaluated in
`enabled`	`boolean`
`overlap`	`string`		skip = don't start if the previous run is still going (guard against pile-up)
`catch_up`	`boolean`		if the scheduler was down over a due time, run once on recovery (else the missed tick is skipped)
`last_run`	`string`		ISO8601 of the last fire (stamped by the scheduler)
`next_run`	`string`		ISO8601 of the next due time (computed by the scheduler)
`last_status`	`string`		outcome of the last run: ok \| error \| skipped-overlap \| <exit-code>