Tunneling Probability Gate

QM8 (T ∝ e^{−2∫√(2m(V−E))/ℏ² dx}): the gate opens only when computed transmission probability clears your threshold.

Category	Quantum
Template ID	tunneling-probability-gate
Definition	tunneling_probability_gate v1.0
States	3 (initial: closed; terminal: latched)
Transitions	3
Operators composed	QM8
Audit clock	on · tick rate 1

What it's for

• Tunnel-junction QA
• STM tip approach control
• Educational quantum demos

States

State	Role
closed	initial
open	intermediate
latched	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
closed	open	QM8	input.transmission >= input.open_threshold	required	—
open	closed	QM8	input.transmission < input.open_threshold	required	—
open	latched	KO42	input.latch == true	no	—

Operators it composes

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

• QM8

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/tunneling-probability-gate

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