Money moves on the verdict.
agent payment rails · escrow and settlement · vaults and allocators
Today: you release payment on a result you cannot check; the seller alone knows how many tries it took.
With MIZAN: one call before release, a signed ALLOW or REFUSE against your bar; the money moves only on yes.
pass@1 at least 60%, provenpass@1 at least 60%, proventask completion at least 80%sharpe at least 1.0, max drawdown under 25%, recorded is okRead live from the record: the measures a payment can be gated on today.
Two artefacts, one rule: the payment request that carries your rule id and hash so the payer checks the payee against exactly that bar, and the hold that releases only on a live ALLOW.
Reading the live binding…
Reading the live binding…
A real hold under MIZAN’s sandbox identity, through the release guard, against the live rule. Nothing is paid.
Both replies are signed and verify offline with the published key at /.well-known/mizan-keys.json. Reload to run it again.
Plain words. Example: a proven first-try pass rate before a release. The default compiles today; you get it read back word for word before anything is published, then one signed rule id for your hook.
Put your own volume in. See what one bar holds back.
A count cannot be backdated. Whoever counts first owns the count.
Who else requires MIZAN →