How do I verify a workflow executed?
To verify a workflow executed, use proof of execution: a linked set of signed proof artifacts, one per required step, that together prove every step ran, in the correct order, to completion. Verification confirms completeness and sequence independently — without trusting the workflow engine and without exposing the process data.
Explanation
Workflows fail silently: steps get skipped, reordered, or only partially completed. A status flag from the workflow engine is a claim you must trust. Proof of execution replaces that claim with verifiable evidence generated as each step runs.
By linking a proof for every step, you can prove not just that the process finished, but that it followed the required sequence — a critical distinction for regulated and cross-organization processes.
How to do it
- 1Define the required steps and their expected order.
- 2Emit a signed proof artifact as each step completes, committing to its data via a hash.
- 3Link the step proofs so their sequence is verifiable.
- 4Emit a completion proof when the final step runs.
- 5Verify each step proof and the linkage to confirm completeness and order.
Examples
KYC onboarding
A four-step KYC workflow proves all steps ran, so a regulator can confirm completion without seeing customer documents.
Right-to-erasure request
A privacy pipeline proves each deletion step executed, evidencing that the request was actually carried out.
Related concepts
Related comparisons
Next steps
See how this works end-to-end in the live demo, or read the cornerstone guide.