🔒All inputs are processed locally in your browser. Nothing is transmitted, stored, or logged. Inputs disappear when you close the tab.

OCG-Industries Showcase · Cluster ⑨ Digital Identity and Credentials

Credential Revocation Audit

A credential that was valid last year may not be valid today, and the usual answer is to trust whichever registry you happened to check. Enter a credential identifier, the lifecycle events applied to it, and the day each event took effect, and this tool derives the credential's current status along with a stamp of the authority and rationale behind it. Re-running the same events reproduces the same status and the same hash, so a revocation can be cited rather than asserted.

Data: event walk over user-entered lifecycle events · no external data

Inputs STEP 1
The licence, registration or credential number as issued. No personal names.
The board, registrar or issuer of record.
Comma separated. Use ISSUE, SUSPEND, REVOKE, REINSTATE. Example: ISSUE,SUSPEND,REINSTATE
A whole number of days since the credential was issued. Enter 0 if the latest event is the issue itself.
Short code recorded by the authority, for example CONDUCT-04 or ADMIN-LAPSE. Leave blank if none.
Status
--
Derived from the event walk
Presentable
--
Only when status is active
Terminal
--
Revoked status cannot be reinstated
Detail
Credential identifier--
Issuing authority--
Events applied--
Latest event day index--
Rationale code--
Reinstate blocked--
Audit key--

This tool accepts a prior artifact handed in from an upstream tool, which raises chain depth to 1; it derives status only from the events entered above, not from the parent artifact.

Policy Mandate v2.0 · what is this?