Earthquake Early Warning

P-wave detected → S-wave imminent → ALERT in the seconds-long window before destructive shaking arrives. Triggers automated shutoffs and public alerts.

Category	Seismology
Template ID	earthquake-early-warning
Definition	earthquake_early_warning v1.0
States	4 (initial: quiet; terminal: all_clear)
Transitions	4
Operators composed	SZ1, SZ2, SZ3, KO42
Audit clock	on · tick rate 1

What it's for

• Public early-warning systems
• Automated gas/rail shutoff
• Critical-facility safe-hold

States

State	Role
quiet	initial
p_detected	intermediate
alert	intermediate
all_clear	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
quiet	p_detected	SZ1	input.p_amplitude > input.p_trigger	required	—
p_detected	alert	SZ2	input.estimated_magnitude >= input.alert_magnitude	required	—
p_detected	quiet	SZ1	input.false_trigger == true	required	—
alert	all_clear	KO42	input.shaking_passed == true	no	—

Operators it composes

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

• SZ1
• SZ2
• SZ3
• 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/earthquake-early-warning

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

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.