Beam Deflection Limit

BEAM_DEFLECTION vs span/360 serviceability limit: within_limit → excessive, with a buckling escalation when the load nears the critical buckling threshold.

Category	Structural Engineering
Template ID	beam-deflection-limit
Definition	beam_deflection_limit v1.0
States	4 (initial: within_limit; terminal: cleared)
Transitions	4
Operators composed	BEAM_DEFLECTION, BUCKLING_CHECK, KO42
Audit clock	on · tick rate 1

What it's for

• Floor / span serviceability
• Temporary-works monitoring
• Formwork load control

States

State	Role
within_limit	initial
excessive	intermediate
buckling_risk	intermediate
cleared	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
within_limit	excessive	BEAM_DEFLECTION	input.deflection_mm > input.span_mm / 360	required	—
excessive	within_limit	BEAM_DEFLECTION	input.deflection_mm <= input.span_mm / 360	required	—
excessive	buckling_risk	BUCKLING_CHECK	input.axial_load_kn > input.critical_buckling_kn * 0.8	required	—
buckling_risk	cleared	KO42	input.load_removed == true	no	—

Operators it composes

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

• BEAM_DEFLECTION
• BUCKLING_CHECK
• 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/beam-deflection-limit

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

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.