Grid Frequency Stability

Monitors grid frequency against the nominal band: nominal → deviation → load-shed before an under-frequency event cascades into a blackout.

Category	Energy & Grid
Template ID	grid-frequency-stability
Definition	grid_frequency_stability v1.0
States	4 (initial: nominal; terminal: restored)
Transitions	4
Operators composed	CT1, POWER_FACTOR, KO42
Audit clock	on · tick rate 1

What it's for

• Microgrid control
• Renewable-heavy grid balancing
• Frequency-response markets

States

State	Role
nominal	initial
deviation	intermediate
load_shed	intermediate
restored	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
nominal	deviation	CT1	input.freq_hz < input.nominal_hz - input.band_hz || input.freq_hz > input.nominal_hz + input.band_hz	required	—
deviation	nominal	CT1	input.freq_hz >= input.nominal_hz - input.band_hz && input.freq_hz <= input.nominal_hz + input.band_hz	required	—
deviation	load_shed	POWER_FACTOR	input.freq_hz < input.shed_hz	required	—
load_shed	restored	KO42	input.frequency_recovered == true	no	—

Operators it composes

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

• CT1
• POWER_FACTOR
• 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/grid-frequency-stability

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

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.