Every artifact a live run produced: transactions, Wormhole messages and their measured finality, Cleanverse answer hashes, policy changes, refusals, and balances before and after.
Canonical happy path
gen 3
One signed intent, cash on Monad and a restricted RWA on Base, both legs delivered and read back from chain state alone.
The run recorded UNKNOWN: “conservation broken: escrow 0 → 0”. That is the runner’s own assertion, not a chain outcome — it compared a resumed run’s closing balances against a mid-flight opening snapshot. The settlement’s chain state and the independent verification below are what say what happened.
Eligible at commit time, refused at delivery time by a RuleV2 the issuer moved in between. The cash leg had already released and was not refunded; the asset leg held, and a disposition resolved it.
One intent composed, checked, signed, prepared, committed, released and settled from the settlement workspace. Every transaction was sent by a wallet in a page, with each next step decided from chain state rather than by a script.
The first live HELD-then-dispositioned settlement, on the generation before the canonical one. It stays verifiable against generation-2 contracts; the current generation cannot answer for it.
A verification is a claim about a settlement under one deployment generation, derived from two chain RPCs, the committed manifests and the guardian set. The application database is not an input.
Served from the repository this Worker was built from, not from object storage. Nothing on this page claims a content-addressed publication that does not exist: ASM-039 stays open, and replacing the storage later changes where these bytes live and nothing about what they mean.