Cascade Failure Risk

NET_BETWEENNESS + PageRank load: resilient → fragile → cascade-risk as load concentrates on critical nodes. For power grids, supply chains, and infra networks.

Category	Network Science
Template ID	cascade-failure-risk
Definition	cascade_failure_risk v1.0
States	4 (initial: resilient; terminal: rebalanced)
Transitions	4
Operators composed	NET_BETWEENNESS, NET_PAGERANK, KO42
Audit clock	on · tick rate 1

What it's for

• Power-grid resilience
• Supply-chain single-points-of-failure
• Telecom backbone planning

States

State	Role
resilient	initial
fragile	intermediate
cascade_risk	intermediate
rebalanced	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
resilient	fragile	NET_BETWEENNESS	input.max_node_load_pct > input.fragile_pct	required	—
fragile	cascade_risk	NET_PAGERANK	input.max_node_load_pct > input.critical_pct	required	—
fragile	resilient	NET_BETWEENNESS	input.max_node_load_pct <= input.fragile_pct	required	—
cascade_risk	rebalanced	KO42	input.load_redistributed == true	required	—

Operators it composes

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

• NET_BETWEENNESS
• NET_PAGERANK
• 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/cascade-failure-risk

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

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.