Threshold Monitor (Generic)

Domain-agnostic watchdog. Watches a stream of reading events; KO42 evaluates the windowed average each fire. normal → breached when the average over the last 60-Zeqond window crosses your limit, with built-in hysteresis (breach at 100, clear at 90) so it won't flap. Emits threshold_breached / threshold_cleared. Point any sensor, KPI, or feed at it.

Category	Foundations
Template ID	threshold-monitor
Definition	threshold_monitor v1.0
States	2 (initial: normal)
Transitions	2
Operators composed	KO42
Audit clock	on · tick rate 1

What it's for

• SLO / metric breach detection
• Sensor or KPI alerting with hysteresis
• Any 'alert when the average crosses X' rule

States

State	Role
normal	initial
breached	intermediate

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
normal	breached	KO42	—	no	on_aggregate · avg(value) > 100 over 60 Zeqonds, event reading · post: emit threshold_breached
breached	normal	KO42	—	no	on_aggregate · avg(value) <= 90 over 60 Zeqonds, event reading · post: emit threshold_cleared

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/threshold-monitor

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

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.