Seismic Early Warning

SZ1 ground-motion watch: quiet → p_wave → alert when peak ground acceleration crosses your threshold. P-wave lead time before the destructive S-wave, with a provable detection log.

Category	Seismology
Template ID	seismic-early-warning
Definition	seismic_early_warning v1.0
States	4 (initial: quiet; terminal: logged)
Transitions	4
Operators composed	SZ1, NM19, KO42
Audit clock	on · tick rate 1

What it's for

• Earthquake early-warning sirens
• Automated gas / rail shutoff
• Structural seismic triggers

States

State	Role
quiet	initial
p_wave	intermediate
alert	intermediate
logged	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
quiet	p_wave	SZ1	input.peak_ground_accel_ms2 > input.p_wave_threshold_ms2	required	—
p_wave	alert	NM19	input.peak_ground_accel_ms2 > input.alert_threshold_ms2	required	—
p_wave	quiet	SZ1	input.peak_ground_accel_ms2 <= input.p_wave_threshold_ms2	required	—
alert	logged	KO42	input.event_logged == true	no	—

Operators it composes

Each transition fires a registry operator: the operator's closed-form solver runs, then the result is proved and verified (compute → prove → verify). The verbatim equation is recorded on the audit row as master_equation_block. This template composes:

• SZ1
• NM19
• 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/seismic-early-warning

# 2. Deploy onto your machine (auth: session; body carries your machine slug)
curl -sS -X POST https://zeqsdk.com/api/contracts/templates/seismic-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": "seismic-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.