Value-at-Risk Breach Monitor

VAR_HISTORICAL + PORTFOLIO_VARIANCE: within_limit → breach → de-risk as the portfolio's VaR crosses the desk's risk limit. Every breach time-stamped on-chain for compliance.

Category	Finance & Risk
Template ID	var-breach-monitor
Definition	var_breach_monitor v1.0
States	4 (initial: within_limit; terminal: compliant)
Transitions	4
Operators composed	VAR_HISTORICAL, PORTFOLIO_VARIANCE, KO42
Audit clock	on · tick rate 1

What it's for

• Trading-desk risk limits
• Fund mandate compliance
• Regulatory risk reporting

States

State	Role
within_limit	initial
breach	intermediate
de_risk	intermediate
compliant	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
within_limit	breach	VAR_HISTORICAL	input.var_usd > input.var_limit_usd	required	—
breach	de_risk	PORTFOLIO_VARIANCE	input.var_usd > input.var_limit_usd * input.hard_multiple	required	—
breach	within_limit	VAR_HISTORICAL	input.var_usd <= input.var_limit_usd	required	—
de_risk	compliant	KO42	input.positions_reduced == true	required	—

Operators it composes

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

• VAR_HISTORICAL
• PORTFOLIO_VARIANCE
• 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/var-breach-monitor

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

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.