Scheduled Compute (Heartbeat)

The automation primitive — a self-firing transition on the HulyaPulse cadence. running → running every 60 Zeqonds (swap every_zeqonds for a cron expression like "0 9 * * 1-5"), emitting scheduled_tick each fire, every tick chain-stamped at the Zeqond it ran. Stop it with a single stop input.

Category	Foundations
Template ID	scheduled-compute
Definition	scheduled_compute v1.0
States	2 (initial: running; terminal: stopped)
Transitions	2
Operators composed	KO42
Audit clock	on · tick rate 1

What it's for

• Periodic recompute / polling jobs
• Cron-style batch kickoffs
• Keep-alive / liveness beacons

States

State	Role
running	initial
stopped	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
running	running	KO42	—	no	recurring · every 60 Zeqonds · post: emit scheduled_tick
running	stopped	KO42	input.stop == true	no	—

Operators it composes

Each transition fires a registry operator through the master equation (compute → prove → verify). This template composes:

• KO42

Browse the operators at /operators/; the building blocks a transition calls are the framework's protocols. KO42 is the always-on substrate operator; physics operators carry proof_required: true, so each fire runs the full compute → prove → verify path and lands a verifiable proof digest on your entangled state.

Deploy it

Inspect the full definition, then deploy it onto your state machine. Every fire is Zeqond-stamped onto your entangled state.

# 1. Inspect — the full definition (states, transitions, operators) as served
curl -sS https://zeqsdk.com/api/contracts/templates/scheduled-compute

# 2. Deploy onto your machine (auth: session; body carries your machine slug)
curl -sS -X POST https://zeqsdk.com/api/contracts/templates/scheduled-compute/deploy \
  -H "Content-Type: application/json" \
  -b "<your session cookie>" \
  -d '{"slug":"<your-machine>"}'
# → 201 { "ok": true, "contract": { "id": "…", "currentState": "running", … },
#         "template_id": "scheduled-compute" }

The deploy path runs the same two-stage validation as the canonical create route (ContractDefinitionSchema.parse + validateContractDefinition against the live registry), writes the creation row onto your entangled state, and schedules the first fire. From there, drive transitions with POST /api/chain/<your-machine>/contracts/<id>/transition or let any triggers fire them autonomously.

Next

• Contract IDE — author, preview, and deploy contracts (this template is in the Templates tab).
• State Contracts — the full contract model: conditions, triggers, pre/post actions, lifecycle.
• Templates Library — every ready-to-deploy contract, grouped by category.
• Protocols — the named building blocks a transition composes.