Receipts and provenance

A durable operation freezes the source revision and input hash for a bot execution. Its operation key, status, result reference and failure reason keep the run identifiable after the definition changes. Numbered steps record the action, input and output references, external source, receipt ID, receipt date and receipt evidence. Together they let the team trace what the bot asked another system to do and what that system confirmed.

The execution workflow marks an operation Succeeded only when the external receipt is confirmed. This check matters when a provider request times out: a missing response does not mean the provider did nothing. The operator can inspect the step and its external identity before deciding whether to reconcile or retry. Evidence documents provide supporting attachments and external references against the definition, with a verifier recorded when the document is checked.

• Operation. The revision, input hash and operation key identify the logical run.
• Step. Each numbered action preserves its input, output and external identities.
• Receipt. A confirmed external receipt supports a successful operation result.

Decide which external system is authoritative for a receipt and which reference is stable enough to reconcile a delayed response. Agree how a provider receipt is attached or referenced and who verifies supporting documents. Define the point at which an uncertain step becomes a reconciliation task. Keep access to receipt evidence limited to the people who need it for operations and review.

Imagine a posting bot that sends one transaction to an external provider. The call returns late, so the step remains uncertain. The operator searches by the external receipt ID and source reference. If the provider confirms the posting, the evidence is recorded on the step and the durable operation can reach Succeeded. If the provider cannot confirm it, the team investigates the same operation key rather than creating an unrelated run.

Open a completed operation. Check that its source revision and input hash match the work that was approved. Follow its numbered steps in order. Each externally executed action should have an input reference and the available output or receipt identity. Compare the receipt evidence with the result reference. Then rehearse a timeout and verify that the team can find the operation without assuming success or issuing a duplicate external action.

• Run steps with uncertain results — Steps marked failed or unknown that need receipt review.
• Verified evidence documents — Documents with recorded verification and external references.
• Durable operations to reconcile — Runs awaiting a confirmed outcome.

See Execute and verify a run and Resolve an exception.