PCR Amplification Cycler

PCR_AMPLIFICATION tracks copy number per cycle: amplifying → plateau → done at target yield, with a no-amplification failure branch. Chain-logged for assay provenance.

Category	Biotech
Template ID	pcr-amplification-cycler
Definition	pcr_amplification_cycler v1.0
States	4 (initial: amplifying; terminal: failed, done)
Transitions	3
Operators composed	PCR_AMPLIFICATION, DNA_MELTING, KO42
Audit clock	on · tick rate 1

What it's for

• Diagnostic qPCR
• Genotyping pipelines
• Synthetic-biology QC

States

State	Role
amplifying	initial
plateau	intermediate
failed	terminal
done	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
amplifying	plateau	PCR_AMPLIFICATION	input.copies >= input.plateau_copies	required	—
amplifying	failed	DNA_MELTING	input.cycle > input.max_cycles && input.copies < input.detection_copies	required	—
plateau	done	KO42	input.target_yield_reached == true	required	—

Operators it composes

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

• PCR_AMPLIFICATION
• DNA_MELTING
• 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/pcr-amplification-cycler

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

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.