How do I verify an approval happened?
To verify an approval happened, check the Proof Artifact for the approval event: a signed record that binds the authenticated provider’s approval event, its payload (as a hash), the issuer, and an anchored timestamp. Verification confirms — mathematically, without trusting the source — that the provider recorded the approval event, that its payload is intact, and where it came from. It does not by itself establish that the approver was authorized or the approval valid; that judgment rests on this evidence.
Explanation
Approvals gate money, access, and risk, which makes them frequent targets of disputes. An approval recorded only in a workflow system can be back-dated, altered, or misattributed, and confirming it requires trusting that system.
A Proof Artifact for the approval event removes that dependency. Because it is signed and commits to the event, payload, and provenance, anyone can independently verify that the provider recorded the approval and detect any tampering — leaving whether the approval was authorized or valid to the business and policy judgment layered on top.
How to do it
- 1Capture the authenticated approval event from the provider that recorded it.
- 2Commit to the event payload with a hash so the details stay private.
- 3Anchor and sign a timestamp to prevent back-dating.
- 4Emit the Proof Artifact for the approval event at the moment it is recorded.
- 5Verify by checking payload integrity, the signature, the issuer’s provenance, and the timestamp.
Examples
High-value payment
A treasury controller approves a wire above threshold; the proof confirms the authorized controller signed off before funds moved.
Privileged access grant
A manager approves admin access. The proof evidences authorized approval, supporting least-privilege controls.
Related concepts
Related comparisons
Next steps
See how this works end-to-end in the live demo, or read the cornerstone guide.