Developer infrastructure for conditional payouts
Money workflows that
carry their own proof.
Payout policies are usually rewritten across application logic, deadlines, retries, and ledger scripts. Pact Runtime compiles one human-approved policy into all of them, verifies the result, and refuses to run if the evidence breaks.
Read-only tour of a completed sandbox run. No account, credentials, or setup required. Every visible hash, balance, and posting is read from stored records.
It extracts an untrusted draft with source evidence. Human approval is the handoff; compilation, verification, authorization, and money movement are deterministic code.
Transition tables, event schemas, ledger scripts, verifier input, and a hash-bound manifest are generated together.
Version checks, intent reservation, durable delivery, and ledger idempotency converge on one recorded settlement.
The demo
One completed run, three levels of evidence
Start with the policy, attack the runtime, then inspect the exact settlement proof.
- 01DefineApprove the exact rules.
See the source policy beside the normalized payout rules and the exact human approval that binds them.
Open Define → - 02BreakTry to pay twice.
Watch release and refund compete for the same agreement. One wins; the other stops before any second settlement exists.
Open Break → - 03ProveFollow the money.
Trace the approved clause through the compiled script and verification report to the exact ledger postings.
Open Prove →
Verification covers the recorded state space, not every imaginable system. The report shows the exact states and transitions explored.