Schedulers

Operator overview of SPEC-179 pluggable schedulers. Each scheduler instance registers with the substrate, heartbeats every ~60s, and claims short-lived leases on agents to dispatch ticks. Trust tiers gate which agents a scheduler can pick up — only system_trusted schedulers can lease privileged agents (treasury, governance, sentinel).

Backed by GET /v1/schedulers (SPEC-179 §3.8) plus a best-effort GET /v1/scheduler/queue per row for runnable counts (§3.5). Surfaces the M45-3 #810 + M47-6 #817 substrate work. Snapshot: 0s ago.

Registered schedulers

No schedulers are registered. Schedulers self-register via POST /v1/schedulers on startup — see SPEC-179 §3.8 for the registration payload.

Active leases

A list-active-leases verb is reserved in SPEC-179 §3.6 but is not yet exposed by the substrate. Today, lease state is only observable via the per-DID lease endpoints:

POST /v1/agents/{did}/lease — grant
POST /v1/agents/{did}/lease/{lease_token}/renew — renew (extend expires_at)
POST /v1/agents/{did}/lease/{lease_token}/release — voluntary release

Once the substrate adds GET /v1/leases, this section will populate without a UI change. Until then, audit lease activity via the privileged-actions log on /privileged-actions and the per-scheduler runnable counts above.