Laser Gain Threshold Gate

PHOT_GAIN_THRESHOLD: below_threshold → lasing → over-drive protection as cavity gain crosses the lasing threshold and then the damage limit.

Category	Photonics
Template ID	laser-gain-threshold
Definition	laser_gain_threshold v1.0
States	4 (initial: below_threshold; terminal: safe)
Transitions	4
Operators composed	PHOT_GAIN_THRESHOLD, PHOT_WAVEGUIDE, KO42
Audit clock	on · tick rate 1

What it's for

• Laser-source bring-up
• Fiber-amplifier protection
• Photonic-IC characterisation

States

State	Role
below_threshold	initial
lasing	intermediate
overdrive	intermediate
safe	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
below_threshold	lasing	PHOT_GAIN_THRESHOLD	input.gain >= input.threshold_gain	required	—
lasing	overdrive	PHOT_WAVEGUIDE	input.output_w > input.damage_w	required	—
lasing	below_threshold	PHOT_GAIN_THRESHOLD	input.gain < input.threshold_gain	required	—
overdrive	safe	KO42	input.pump_reduced == true	no	—

Operators it composes

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

• PHOT_GAIN_THRESHOLD
• PHOT_WAVEGUIDE
• 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/laser-gain-threshold

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

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.