Vickers Hardness QA

HARDNESS_VICKERS acceptance per part: pass → fail against the heat-treat spec window, with statistical-drift escalation across a batch.

Category	Material Science
Template ID	vickers-hardness-qa
Definition	vickers_hardness_qa v1.0
States	4 (initial: sampling; terminal: accepted)
Transitions	3
Operators composed	HARDNESS_VICKERS, MATERIAL_STRENGTH, KO42
Audit clock	on · tick rate 1

What it's for

• Heat-treatment QA
• Tooling acceptance
• Surface-hardening verification

States

State	Role
sampling	initial
fail	intermediate
batch_drift	intermediate
accepted	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
sampling	fail	HARDNESS_VICKERS	input.hv < input.hv_min || input.hv > input.hv_max	required	—
sampling	batch_drift	MATERIAL_STRENGTH	input.hv_stddev > input.drift_limit	required	—
sampling	accepted	KO42	input.batch_complete == true	required	—

Operators it composes

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

• HARDNESS_VICKERS
• MATERIAL_STRENGTH
• 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/vickers-hardness-qa

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

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.