ScheduleDefinition

One coherent definition edit. The document boundary rejects revision 0 and any edit that does not advance exactly once.

Type object

Shape

Field	Type	Description
revisionrequired	integer (uint32, >= 0)
effective_at_msrequired	integer (int64)	The inclusive lower bound for occurrences under this revision. Edits and resumes advance it, so a new rule cannot catch up older slots.
templaterequired	DelegationTemplate	The reusable request fields. `RunId`, executing device, and document version pins exist only for one claimed firing and cannot be stored here.
recurrencerequired	RecurrenceRule	A persisted recurrence rule. The variants preserve Koru's existing floating-versus-zoned distinction without an optional timezone.
lifecyclerequired	ScheduleLifecycle

Example

{
  "revision": 0,
  "effective_at_ms": 0,
  "template": {
    "requested_by": {
      "profile": "00000000-0000-4000-8000-000000000000",
      "kind": "person"
    },
    "objective": "string",
    "agent": {
      "kind": "built_in",
      "value": "string"
    },
    "requested_model": "string",
    "scope": {
      "kind": "none"
    },
    "grants": [],
    "context": []
  },
  "recurrence": {
    "cron": "string",
    "type": "floating"
  },
  "lifecycle": "active"
}

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Generated from contract version 1. Last updated November 12, 2026.