Approval Workflow (N-of-M)

Multi-party sign-off as a contract. pending → approved once N approve events land (default 3), or → rejected the moment a single reject event arrives. Every signature is a tamper-evident row on the entangled state — who approved, at which Zeqond. Drop-in for deploy gates, change control, payouts, clinical orders.

Category	Foundations
Template ID	approval-workflow
Definition	approval_workflow v1.0
States	3 (initial: pending; terminal: approved, rejected)
Transitions	2
Operators composed	KO42
Audit clock	on · tick rate 1

What it's for

• Release / deploy approval gates
• Change-control & sign-off
• Multi-sig style authorizations

States

State	Role
pending	initial
approved	terminal
rejected	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
pending	approved	KO42	—	no	on_aggregate · count >= 3 over 1000000 Zeqonds, event approve · post: emit approval_granted
pending	rejected	KO42	—	no	on_event · reject · post: emit approval_denied

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/approval-workflow

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

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.