Data Pipeline

Ingest → validate → publish with failure branches; every stage transition is an audited, Zeqond-stamped fact.

Category	Operations
Template ID	data-pipeline
Definition	data_pipeline v1.0
States	4 (initial: ingesting; terminal: published, failed)
Transitions	3
Operators composed	CS47, KO42
Audit clock	on · tick rate 1

What it's for

• ETL state tracking
• Dataset releases
• Compliance-grade data lineage

States

State	Role
ingesting	initial
validating	intermediate
published	terminal
failed	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
ingesting	validating	KO42	input.batch_complete == true	no	—
validating	published	CS47	input.validation_error_rate <= input.max_error_rate	required	—
validating	failed	CS47	input.validation_error_rate > input.max_error_rate	required	—

Operators it composes

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

• CS47
• 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/data-pipeline

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

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.