Six templates.
One grammar underneath.
What changes between a transfer and an agent job is the evidence lane, not the mechanism. Each template below names the lanes the layer can decode, the failure it exists to price, and what the acceptance digest seals before work begins.
Value moves from one chain to another
A transfer whose destination event the layer decodes against the anchored root. The money either lands or comes back, provably, on a deadline.
It never arrives and the refund sits in limbo. One bridge failure stranded $292M in April 2026; this template is the answer to that shape.
The payout tuple: asset, amount, recipient, chain.
A remote call with an expected result
A cross-chain message or contract call. Evidence is the execution event plus the return-data digest carried in the delivery envelope.
Executed on the far side, but wrong. The digest mismatches the sealed acceptance and the escrow reclaims.
The return-data digest.
A workflow or agent job
The automation-platform class. Evidence arrives through a log sink, a node emitting envelopes in-flow, or the settler itself acting as a tool the agent calls.
The workflow reports success and the business result did not happen. Nobody independently checked, because until now nobody could.
A machine-checkable spec, or a bonded evaluator's grade for judgment calls.
A paid response
The metered-API class. Rides the batch-settlement channel, so one position covers a channel's whole day of micro-calls.
A paid response that was wrong, or never came, and is far too small to dispute individually.
The response digest carried in the voucher flow.
Micro-insurance without micro-overhead: the premium is a fraction on the channel, not a per-call toll.
Recurring metered work
Subscriptions, keeper duty, standing automation. Each epoch is one operation under one standing profile.
The keeper did not fire in the epoch where it mattered.
The per-epoch delivery condition; void epochs pay nobody.
The escape hatch that is not an escape
A custom profile with declared evidence lanes, admitted only if it passes the five-property test and ships a conformance fixture.
Whatever the operation's own failure is — but it must be decodable first.
Declared per profile, sealed like any other.
ANY without a decodable lane does not exist here.
How evidence reaches the layer for work that does not happen on a chain. These are transports, not new operations: each lands in the same two calls. Every one of them needs the operator's consent — there is no passive subscription to a stranger's work, and we should never claim otherwise.
An enterprise workflow platform streams every workflow, node and audit event to a webhook we sink and sign.
Operator enables the stream. Enterprise tier.
A node dropped inside the workflow emits a signed envelope per execution: workflow id, version digest, input and output digests, outcome.
Operator installs the node. No enterprise tier needed.
The platform's own REST API lists executions, scoped by the owner's API key. We poll their work directly, with their key.
Operator issues a key.
Their trigger exposes a workflow as a tool the gate can hire; our gadget ships as a tool their agents call. A declared job needs no surveillance at all.
Mutual, per call. The strongest lane.