Flow Regime Monitor

FL1 Reynolds-number watch: laminar → transitional → turbulent as Re = ρvL/μ crosses 2300 and 4000. Pipe-flow and aerodynamics regime classification with a provable transition log.

Category	Fluid Dynamics
Template ID	flow-regime-monitor
Definition	flow_regime_monitor v1.0
States	4 (initial: laminar; terminal: recorded)
Transitions	4
Operators composed	FL1, KO42
Audit clock	on · tick rate 1

What it's for

• Pipeline flow assurance
• Wind-tunnel regime tagging
• HVAC duct design checks

States

State	Role
laminar	initial
transitional	intermediate
turbulent	intermediate
recorded	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
laminar	transitional	FL1	input.reynolds_number > 2300	required	—
transitional	turbulent	FL1	input.reynolds_number > 4000	required	—
transitional	laminar	FL1	input.reynolds_number <= 2300	required	—
turbulent	recorded	KO42	input.run_complete == true	no	—

Operators it composes

Each transition fires a registry operator: the operator's closed-form solver runs, then the result is proved and verified (compute → prove → verify). The verbatim equation is recorded on the audit row as master_equation_block. This template composes:

• FL1
• 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/flow-regime-monitor

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