Von Mises Yield Gate

STRESS_VON_MISES on live load data: safe → yielding → plastic as the equivalent stress approaches the material's yield strength. The structural-integrity tripwire.

Category	Structural Engineering
Template ID	von-mises-yield-gate
Definition	von_mises_yield_gate v1.0
States	4 (initial: safe; terminal: locked_out)
Transitions	4
Operators composed	STRESS_VON_MISES, STRESS_PRINCIPAL, KO42
Audit clock	on · tick rate 1

What it's for

• Pressure-vessel monitoring
• Crane / lifting-gear safety
• Bridge load gating

States

State	Role
safe	initial
yielding	intermediate
plastic	intermediate
locked_out	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
safe	yielding	STRESS_VON_MISES	input.von_mises_mpa > input.yield_mpa * input.safety_factor	required	—
yielding	safe	STRESS_VON_MISES	input.von_mises_mpa <= input.yield_mpa * input.safety_factor	required	—
yielding	plastic	STRESS_PRINCIPAL	input.von_mises_mpa > input.yield_mpa	required	—
plastic	locked_out	KO42	input.shutdown == true	no	—

Operators it composes

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

• STRESS_VON_MISES
• STRESS_PRINCIPAL
• 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/von-mises-yield-gate

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

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.