Scheduler

Schedules are declared by Agent Cores and executed by the host.

Runtime State

Core-authored schedules live under:

agent/schedules/*.yaml

Host scheduler state is projected into:

~/.demiurge/runtime/runtime.sqlite3

The scheduler_instances projection records due times, task ids, claim status, idempotency keys, claim ids, and lease expiry. Each due occurrence also has a schedule.fire durable work item claimed through HostWorkLifecycleRuntime. Older ~/.demiurge/scheduler/ JSON files are not read, migrated, or dual-written by the runtime.

Claim Flow

The scheduler computes due times from cron expressions and runtime timezone. When a schedule is due, the host claims the durable work item with a claim token and lease through the host work lifecycle, records the SQLite scheduler claim, advances the next run time, and creates a runtime task using an idempotency key derived from core id, schedule id, and due time. Completion must compare the claim token; stale completions from an expired claim are rejected.

Run Flow

Each run creates a fresh scheduled session with synthetic inbound metadata. The runner executes the schedule prompt using the schedule-selected input and output modules.

Delivery

Local delivery stays in local session records. External delivery validates the configured channel and target before sending.

Boundary

The Agent Core declares schedules. The host owns durable run state, claims, run records, session creation, and channel delivery. Operator surfaces should read schedule work through HostWorkLifecycleRuntime when they need one view across schedules, delivery, detached tasks, and completion inbox work.