ART-287 · Compliance · REVOKE-R1

Revocation-Status Verifier

Checks a receipt's optional credentialStatus reference (W3C BitstringStatusList, SPEC.md §REVOKE-1) and reads the revocation bit at statusListIndex in a supplied (zero-egress, never fetched) status list credential. A set bit means revoked, and revocation overrides §16 signature validity even when the receipt's own signature is cryptographically valid. Absence of a status reference is its own no-signal state, never treated as evidence of active status.

W3C BitstringStatusList Revocation Overrides Signature Absence ≠ Known-Good
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
What this does NOT prove
This kernel never dereferences statusListCredential over the network: the status list credential's encoded bitstring must be supplied as an input. It does not validate the status list credential's own §16 signature, does not decompress a GZIP-encoded W3C encodedList (test-side fixtures use this kernel's own uncompressed base64url encoding, not the published SDK vectors), and a "no-signal" result is not a positive claim of active status; it means no status reference was checkable, nothing more.
Receipt credentialStatus (optional)
Status List Credential (supplied input, zero-egress)
–
Status
–
List Index
Revocation check
⚠ DECISION-SUPPORT DRAFT. Not an audit and not a PCAOB opinion. See the "What this does NOT prove" note above.
OpenChainGraph v0.4 artifact · execution_hash:
–


    

      
      
      
    

  


  
  









  

    
Ask your agent

    
  

  
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

  
Run the AINumbers MCP tool `verify_revocation_status`. Task: Check a receipt's optional W3C BitstringStatusList credentialStatus reference and reads the revocation bit at statusListIndex from a supplied, zero-egress status list credential.
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-287-revocation-status-verifier.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA