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 step event, that together evidence each authenticated step event was recorded, its payload is intact, and its order. Verification confirms this independently — without trusting the workflow engine and without exposing the process data. It evidences the reported events, not whether the workflow was business-correct.
Explanation
Workflows report step events that are later disputed. A status flag from the workflow engine is a claim you must trust. Proof of Execution replaces that claim with independently verifiable Proof Artifacts generated as each step reports an event.
By linking a Proof Artifact for every step event, you can evidence not just that events were reported but the order in which they were reported — a critical distinction for regulated and cross-organization processes. Whether the process was correct in business terms is judged on top of this evidence.
How to do it
- 1Enumerate the step events you expect and their order.
- 2Emit a signed Proof Artifact as each step reports an event, committing to its payload via a hash.
- 3Link the step artifacts so their sequence is verifiable.
- 4Emit a completion artifact when the final step reports its event.
- 5Verify each artifact and the linkage to confirm payload integrity 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.