OPEN
Commit before work
The preview starts from a work order with prepared escrow terms, evidence rules, parties, and a pre-work commitment hash.
GENLAYER RUNNER · RELEASE / REFUND / ESCALATE · PRIVATE PREVIEW
The work starts only after escrow terms and evidence rules are committed.
Gregers shows the lifecycle a GenLayer-style contract could run: open work order, bind Concordium evidence, accept work, adjudicate, then prepare release, refund, or escalation.
Why now: agent commerce needs pre-work accountability, not only post-hoc receipts.
1. Opencommit work order
2. Bindattach Concordium evidence
3. Adjudicatesimulate verdict
4. Preparerelease/refund/escalate
5. Receipthash-bound runner proof
Boundary: simulated runner only. No live GenLayer contract, no validator call, no escrow lock, no payment, no settlement, no fulfilment, no WalletConnect, no raw identity disclosure, no new Concordium transaction. Not official Concordium/Foundation or GenLayer output.
Ask for GenLayer/Concordium reviewers: should this open → bind evidence → adjudicate → prepare release/refund/escalate lifecycle be the contract/escrow intake shape before agent work starts?
ADJUDICATE
Simulate verdict
Select release, refund, insufficient evidence, scope mismatch, expired receipt, or missing preimage to test fail-closed lifecycle outcomes.
OUTCOME
Prepare, do not execute
The runner produces a hash-bound receipt for release/refund/escalation states. It never moves funds or calls GenLayer.
Run lifecycle preview
Click the button to simulate a no-side-effect runner receipt.
RELEASE
Release prepared
Positive verdict prepares release after finality in a real integration; no funds move here.
REFUND
Refund prepared
Negative verdict prepares refund or refund/escalation; no refund is executed here.
ESCALATE
Escalation prepared
Insufficient, expired, or missing evidence requests more proof before any release.
Raw hash-bound runner receipt JSON
Waiting for preview…