For protocols · gate 01 of five

Code decides on the verdict.

vaults and strategy protocols · oracles and data networks · agent registries and directories · bounty and grant platforms · compute and inference markets · device and fleet operators

Today: a contract or a config releases, routes or allocates on a number nobody re-checked.
With MIZAN: one signed message your code checks before it acts; no human in the loop, no trust in the seller.

A worked example
Before
A vault routes 400,000 to a strategy because its dashboard shows Sharpe 2.1; the operator ran 300 variants and showed the best.
The bar
sharpe at least 1.0, max drawdown under 25%, at least 20 trades, recorded is ok
After
The vault contract checks the signed verdict before it routes; the 300 attempts are counted, the corrected result is REFUSE, nothing moves.
More cases
oracle networka reporter earns the next aggregation slot only on a signed verdict
hit rate at least 80%, recorded is ok
bounty platforma payout releases on a counted milestone
task completion at least 80%
fleet operatora dispatcher routes jobs to a counted device record
uptime at least 99%
01 · Your measures

Read live from the record: the measures a code gate can require today, and the two drafted next.

Reading the live list…
02 · Your hook

The code gate: a seven-field message, canonical JSON, one Ed25519 signature. Your contract or config verifies it offline with the published key and acts only on ALLOW. Same rule id, same hash, same verdict as every other hook.

json · the code gate · schema + how to verify · fetched live for rule req_b68b0bb66d46@1
Reading the live binding…
03 · See it work

The code-gate message for the subject try-me, rendered from the live check reply, then verified in your browser.

the code-gate message for try-me · live · seven fields, one signature
Asking the record…

verify: Ed25519 over the canonical JSON with the published key.

04 · Write your bar

Plain words. Example: a proven first-try pass rate before your code routes to a model. The default compiles today; you get it read back word for word before anything is published, then one signed rule id for your hook.

A count cannot be backdated. Whoever counts first owns the count.

Who else requires MIZAN →
Set the bar your code checks →