RNG Entropy Health Gate

CRYPTO_ENTROPY on a random source: healthy → degraded → fail, holding key generation when entropy drops below the security floor. Prevents weak-key disasters.

Category	Cryptography
Template ID	rng-entropy-health
Definition	rng_entropy_health v1.0
States	4 (initial: healthy; terminal: reseeded)
Transitions	4
Operators composed	CRYPTO_ENTROPY, CRYPTO_HASH_COLLISION, KO42
Audit clock	on · tick rate 1

What it's for

• HSM / key-gen pipelines
• IoT secure provisioning
• TLS certificate issuance

States

State	Role
healthy	initial
degraded	intermediate
fail	intermediate
reseeded	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
healthy	degraded	CRYPTO_ENTROPY	input.entropy_bits_per_byte < input.warn_floor	required	—
degraded	fail	CRYPTO_HASH_COLLISION	input.entropy_bits_per_byte < input.security_floor	required	—
degraded	healthy	CRYPTO_ENTROPY	input.entropy_bits_per_byte >= input.warn_floor	required	—
fail	reseeded	KO42	input.reseeded == true	required	—

Operators it composes

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

• CRYPTO_ENTROPY
• CRYPTO_HASH_COLLISION
• 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/rng-entropy-health

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

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.