Scheduler

The scheduler is the daemon subsystem that decides when work runs, how much runs in parallel, and what happens when execution fails. It combines cron-driven routine firing, event-reactive signal dispatch, and budget-aware concurrency control into a single coordination layer. Every Signal that enters the system — whether from a scheduled Routine, an external event, or an inter-agent message — flows through the scheduler before reaching an agent's Work Pile.

Tick Loop

Tick Loop — How the daemon's core event loop drives continuous operation — monitoring channels, firing routines, processing the dead letter queue, and evaluating the risk registry on each pass.

Cron Triggers

Cron Triggers — Routines that fire on cron schedules, emitting Signals into the work lifecycle. Covers schedule syntax, scope levels (org/project/team/agent), missed-fire tracking, and retry policies.

Job Queue

Job Queue — The Work Pile — each agent's ordered queue of pending assigned work — and how Signals are enqueued at priority, interrupted for urgency, or held when an agent is at zero bandwidth.

Wave Dispatch

Wave Dispatch — How the runtime batches mutually independent Work Items into waves for parallel execution, manages a fixed-size worker pool, and synchronizes on wave completion before advancing.

Concurrency Limits

Concurrency Limits — Budget Gate enforcement during dispatch — configurable parallel run caps per scope, and the gate behaviors (queue, reduce-scope, warn) that activate when budget would be exceeded.

Priority and Ordering

Priority and Ordering — How inbound Signals are triaged by urgency, routed by priority (direct-agent, group, subscription, fallback), and ordered within an agent's Work Pile.

Retry and Backoff

Retry and Backoff — Failure classification for retryable vs. terminal outcomes, grounding-instruction injection on retry, context-window exhaustion recovery, and escalation paths when retries are exhausted.