Photon Budget Counter
QM10 (E = hν): integrates photon energy over a window — counting → saturated when the dose budget for a sample or sensor is spent.
| Category | Quantum |
| Template ID | photon-budget-counter |
| Definition | photon_budget_counter v1.0 |
| States | 3 (initial: counting; terminal: reset) |
| Transitions | 2 |
| Operators composed | QM10 |
| Audit clock | on · tick rate 1 |
What it's for
- Fluorescence-microscopy dose limits
- Photoresist exposure
- Detector protection
States
| State | Role |
|---|---|
counting | initial |
saturated | intermediate |
reset | terminal |
Transitions
| From | To | Operator | Fires when | Proof | Trigger / actions |
|---|---|---|---|---|---|
counting | saturated | QM10 | input.dose_joules >= input.budget_joules | required | — |
saturated | reset | KO42 | input.sample_swapped == true | no | — |
Operators it composes
Each transition fires a registry operator through the master equation (compute → prove → verify). This template composes:
QM10
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/photon-budget-counter
# 2. Deploy onto your machine (auth: session; body carries your machine slug)
curl -sS -X POST https://zeqsdk.com/api/contracts/templates/photon-budget-counter/deploy \
-H "Content-Type: application/json" \
-b "<your session cookie>" \
-d '{"slug":"<your-machine>"}'
# → 201 { "ok": true, "contract": { "id": "…", "currentState": "counting", … },
# "template_id": "photon-budget-counter" }
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.