Spectral Line Classifier

Identifies elements from emission/absorption lines: scanning → identified → flagged when an unexpected line appears. Real-time spectroscopy with a provable detection log.

Category	Atomic Physics
Template ID	spectral-line-classifier
Definition	spectral_line_classifier v1.0
States	4 (initial: scanning; terminal: logged)
Transitions	4
Operators composed	XION_1, XION_2, KO42
Audit clock	on · tick rate 1

What it's for

• Industrial materials sorting
• Environmental contaminant ID
• Lab spectroscopy automation

States

State	Role
scanning	initial
identified	intermediate
flagged	intermediate
logged	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
scanning	identified	XION_1	input.line_match_confidence > input.match_threshold	required	—
scanning	flagged	XION_2	input.unexpected_line == true	required	—
identified	logged	KO42	input.recorded == true	no	—
flagged	logged	KO42	input.recorded == true	no	—

Operators it composes

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

• XION_1
• XION_2
• 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/spectral-line-classifier

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

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.