Alloy Spec Compliance

ALLOY_MIXTURE checks a melt's composition against spec bands: in_spec → out_of_spec → rejected. Every heat's certificate is chain-stamped — provable provenance.

Category	Material Science
Template ID	alloy-spec-compliance
Definition	alloy_spec_compliance v1.0
States	4 (initial: in_spec; terminal: rejected, certified)
Transitions	4
Operators composed	ALLOY_MIXTURE, MATERIAL_MODULUS, KO42
Audit clock	on · tick rate 1

What it's for

• Foundry QA
• Aerospace-grade alloy certification
• Supplier acceptance testing

States

State	Role
in_spec	initial
out_of_spec	intermediate
rejected	terminal
certified	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
in_spec	out_of_spec	ALLOY_MIXTURE	input.composition_error_pct > input.spec_tolerance_pct	required	—
in_spec	certified	MATERIAL_MODULUS	input.batch_complete == true && input.composition_error_pct <= input.spec_tolerance_pct	required	—
out_of_spec	rejected	KO42	input.disposition == 'scrap'	required	—
out_of_spec	in_spec	ALLOY_MIXTURE	input.composition_error_pct <= input.spec_tolerance_pct	required	—

Operators it composes

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

• ALLOY_MIXTURE
• MATERIAL_MODULUS
• 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/alloy-spec-compliance

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

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.