Skip to content

Execution receipts

An execution receipt records evidence of what happened after dispatch. A provider may return a delivery ID, a confirmed order, or an identifier for the record it updated. Keep the receipt with the run and the approval it consumed.

Associate the receipt with the workspace, run, step and reviewed proposal. Keep the operation, target, acting account reference, provider result, timing, and actual usage that are available. Store sensitive evidence under its workspace access policy. A provider response can confirm that a request was accepted while the eventual external result is still pending.

Illustrative timeline for a connector that accepts a write and finishes it asynchronously.

Approved → dispatched → provider job ID recorded → waiting for completion
→ provider status confirmed → receipt attached to the run
Observation Next action
No dispatch occurred Recheck the current grant and proposal before retrying
Provider confirms the effect happened Attach the provider result and continue from the confirmed state
Provider confirms rejection Record the failure and decide whether the same reviewed request can be retried
Connection failed after dispatch Look up the operation by durable identity or ask an authorized person to reconcile

Keep rehearsal evidence and live receipts separately identifiable. The draft specifies this behavior and leaves a portable receipt schema open. Gabriel execution details and events expose attempt state in the workspace.

See runs, the dispatch rules, and live sync.