Heat Exchanger Fouling Monitor

THERMO_HEAT_TRANSFER effectiveness decline: clean → fouling → clean-now as the heat-transfer coefficient drops below the cleaning threshold. Schedules maintenance on physics, not the calendar.

Category	Thermodynamics
Template ID	heat-exchanger-fouling
Definition	heat_exchanger_fouling v1.0
States	4 (initial: clean; terminal: serviced)
Transitions	4
Operators composed	TH1, TH2, KO42
Audit clock	on · tick rate 1

What it's for

• Refinery / chemical plant
• HVAC chiller maintenance
• Power-plant condensers

States

State	Role
clean	initial
fouling	intermediate
clean_now	intermediate
serviced	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
clean	fouling	TH1	input.u_coefficient < input.clean_u * input.fouling_fraction	required	—
fouling	clean_now	TH2	input.u_coefficient < input.clean_u * input.cleaning_trigger	required	—
fouling	clean	TH1	input.u_coefficient >= input.clean_u * input.fouling_fraction	required	—
clean_now	serviced	KO42	input.cleaned == true	required	—

Operators it composes

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

• TH1
• TH2
• 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/heat-exchanger-fouling

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

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.