VRX-1 · Receipt Type 4 · Refusal

Say no professionally, transparently, and reviewably.

A Refusal Receipt records that an institution or a person declined a request, application, signature, payment, consent, submission, or AI output — with the reason documented, the missing or required items named, and a correction or appeal path stated. Institutional and personal modes. The receipt is self-attested by its creator; its content is tamper-evident via SHA-256.

What a Refusal Receipt is

A structured record that someone refused something at a recorded moment, with the reason named and a correction or appeal path stated. Two locked modes:

  • Institutional Refusal Receipt — We did not reject you arbitrarily. Here is the documented reason, the missing item, and the correction or appeal path.
  • Personal Refusal Receipt — I refused to sign, pay, consent, submit, agree, delete, share, or accept because the request was unclear, unsafe, unsupported, or incomplete.

Refusal receipts are a durable advantage in an AGI era: a person or institution that can refuse with a documented reason and a correction path protects everyone — the refuser, the refused party, and any later reviewer.

What this receipt proves

  • The receipt content has not been altered since the hash was computed — anyone holding the JSON can recompute the SHA-256 and confirm a match.
  • A creation timestamp recorded by the device that built the receipt.
  • A self-attestation by the creator that a refusal occurred on the stated date for the stated reasons.

What this receipt does not prove

  • That the refusal is lawful or reasonable. Lawfulness and reasonableness are decided by the receiving party or a reviewing authority.
  • That the facts inside the receipt are true. The receipt is self-attested by its creator.
  • That the receipt is signed by an institutional issuer. The current reference implementation uses no signing key.
  • That the timestamp is anchored to an external clock or registry. The timestamp is taken from the device that built the receipt.
  • That any regulator, court, board, employer, university, or platform must accept the refusal. Acceptance is decided by the receiving party.

Truth-boundary preserved

PlenaProof does not provide legal advice. PlenaProof does not adjudicate whether a refusal is lawful or proportionate. PlenaProof helps a refuser document the refusal so it can be reviewed. A Refusal Receipt is an organised record of a refusal event, formatted so a counterparty, a regulator, a court, a board, an employer, a university, a donor, a partner, or a public agency can read it. It is not a court order, not a regulator's determination, not a binding decision, and not an official rejection by any external authority.

Future production releases may add issuer signing keys, external timestamp anchoring, a public revocation registry, and certified-issuer status. These remain roadmap items.

Show schema preview (technical)

Refusal Receipt v1 inherits the established VRX-1 schema conventions. All keys are alphabetised before hashing; the hash field is computed over the canonical JSON with the hash field itself removed. The published schema file is vrx1-refusal-receipt.schema.json.


  







  

    
Build a Refusal Receipt on this device

    
All processing happens in your browser. Nothing is sent to a server. The receipt JSON, hash, and verification URL are produced locally and can be exported, printed, or saved to the local Vault preview.


    

      

        
        
      

      

        
        
        
Use a role title or pseudonym if the public receipt should not name the refuser directly.

      

      

        
        
      

      

        
        
      

      

        
        
      

      

        
        
      

      

        
        
      

      

        
        

          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
        

      

      

        
        
      

      

        
        
      

      

        
        
      

      

        
        
      

      

        
        
        
If the refusal addresses a prior submission, name it here.

      

      

        
        
        
If the refusal follows a documented human review, name the review receipt here.

      

      

        
        
      

      

        
        
      

      

        
        
        
If this refusal corrects or replaces an earlier one, name it here.

      

    


    

      
      
    


    
Privacy reminder. This page runs only in your browser. Nothing is uploaded. If you save the receipt to the Vault preview, it is stored on this device only. Anyone with the JSON file can read its contents — redact private items before sharing.

  


  






  

    
Verify a Refusal Receipt

    
Paste a receipt JSON or upload a .json file. The page recomputes the SHA-256 over the canonical JSON (with the hash field removed) and compares it to the hash stored inside the receipt. A match means the receipt content has not been modified since the hash was computed; it does not mean the refusal was lawful or reasonable, or that any external authority must accept the receipt.


    

      

        
        
      

      

        
        
      

    


    

      
      
    

  


  






  

    
Saved on this device

    
Receipts you save to the local Vault preview are stored only on this browser, across all VRX-1 receipt-type pages. They are not synced and not uploaded. Clearing browser data on this device removes them.

    
No saved receipts yet on this device.