Diffraction Limit Gate

Rayleigh resolution check: resolved → unresolved as feature spacing falls below the diffraction limit for the system's NA and wavelength. Imaging / metrology QA.

Category	Optics
Template ID	diffraction-limit-gate
Definition	diffraction_limit_gate v1.0
States	3 (initial: resolved; terminal: recalibrated)
Transitions	3
Operators composed	OP1, OP2, KO42
Audit clock	on · tick rate 1

What it's for

• Microscopy resolution QA
• Lithography metrology
• Telescope commissioning

States

State	Role
resolved	initial
unresolved	intermediate
recalibrated	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
resolved	unresolved	OP1	input.feature_spacing_nm < input.rayleigh_limit_nm	required	—
unresolved	resolved	OP2	input.feature_spacing_nm >= input.rayleigh_limit_nm	required	—
unresolved	recalibrated	KO42	input.optics_adjusted == true	no	—

Operators it composes

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

• OP1
• OP2
• 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/diffraction-limit-gate

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