Transformer Overload Guard

POWER_LOSS + thermal model: normal → overloaded → trip as winding temperature and loss exceed the unit's rating. Extends asset life, prevents fires.

Category	Energy & Grid
Template ID	transformer-overload-guard
Definition	transformer_overload_guard v1.0
States	3 (initial: normal; terminal: trip)
Transitions	3
Operators composed	POWER_LOSS, POWER_ELECTRICAL, KO42
Audit clock	on · tick rate 1

What it's for

• Distribution-transformer protection
• EV-charging-cluster loads
• Industrial substation ops

States

State	Role
normal	initial
overloaded	intermediate
trip	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
normal	overloaded	POWER_ELECTRICAL	input.load_kva > input.rating_kva	required	—
overloaded	normal	POWER_ELECTRICAL	input.load_kva <= input.rating_kva	required	—
overloaded	trip	POWER_LOSS	input.winding_temp_c > input.trip_temp_c	required	—

Operators it composes

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

• POWER_LOSS
• POWER_ELECTRICAL
• 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/transformer-overload-guard

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

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.