Supply-Chain Provenance

Tamper-evident custody chain. Each handoff event advances the chain and emits custody_changed; a delivered event closes it. Every hop is Zeqond-stamped on the entangled state, so the full provenance is verifiable end to end. Drop-in for logistics, cold-chain, and parts traceability.

Category	Foundations
Template ID	supply-chain-provenance
Definition	supply_chain_provenance v1.0
States	3 (initial: origin; terminal: delivered)
Transitions	3
Operators composed	KO42
Audit clock	on · tick rate 1

What it's for

• Logistics chain-of-custody
• Cold-chain / pharma traceability
• Parts & materials provenance

States

State	Role
origin	initial
in_transit	intermediate
delivered	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
origin	in_transit	KO42	—	no	on_event · handoff · post: emit custody_changed
in_transit	in_transit	KO42	—	no	on_event · handoff · post: emit custody_changed
in_transit	delivered	KO42	—	no	on_event · delivered · post: emit chain_closed

Operators it composes

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

• 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/supply-chain-provenance

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

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.