Thermal Expansion Mismatch Guard

THERMAL_EXPANSION on a bonded joint: bonded → stressed → delaminating as differential expansion across two materials exceeds the interface tolerance.

Category	Material Science
Template ID	thermal-expansion-mismatch
Definition	thermal_expansion_mismatch v1.0
States	4 (initial: bonded; terminal: failed)
Transitions	4
Operators composed	THERMAL_EXPANSION, MATERIAL_MODULUS, KO42
Audit clock	on · tick rate 1

What it's for

• Electronics solder-joint reliability
• Composite-metal bonding
• Cryogenic vessel design

States

State	Role
bonded	initial
stressed	intermediate
delaminating	intermediate
failed	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
bonded	stressed	THERMAL_EXPANSION	input.differential_strain > input.interface_strain_limit * 0.7	required	—
stressed	bonded	THERMAL_EXPANSION	input.differential_strain <= input.interface_strain_limit * 0.7	required	—
stressed	delaminating	MATERIAL_MODULUS	input.differential_strain > input.interface_strain_limit	required	—
delaminating	failed	KO42	input.bond_lost == true	required	—

Operators it composes

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

• THERMAL_EXPANSION
• MATERIAL_MODULUS
• 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/thermal-expansion-mismatch

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

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.