Problem Deploy Demo Regulations Security Pricing Request Access

PlainReal  /  Record Explorer

Record
Explorer

Every field in a record exists for a specific forensic reason. Click any field in the JSON to see what it proves and why it matters. Toggle between decorator and auto-instrument capture layers. Run the simulated verification CLI.

⚠This is a real record, not a mock-up. It is the sample the public verifier at verify.plainreal.com ships and checks, and its Ed25519 signature is valid — so if you download it and verify it yourself, it passes. Editing any byte breaks that signature, which is the point. The subject is synthetic: org:acme-lending, no real applicant. It carries no RFC 3161 token, so it evidences content rather than time. The design-partner substrate signs in software; production signs inside a FIPS 140-2 Level 3 HSM, with the same algorithm and the same schema.
33 fields  ·  record schema
Download demo_record.json
demo_record.json  ·  BUSINESS_LAYER TIER-A · consequential=true 

          

        

        

          Click any highlighted field to see what it proves →
        

      


      
      


        
        

          

            
Click a field in the JSON

            
. select a field .

          

          

            What does each field prove?
            Click any field in the JSON on the left to see its forensic purpose. what it captures, why it's in the artifact, and which regulatory requirement it satisfies.
          

        


        
        

          

            plainreal verify. standalone CLI simulation
            

              

                
                
              

              
            

          

          

            Click "Run verify" to simulate the standalone verification CLI. Past artifacts are independently verifiable using only the published public key. Your auditor runs this themselves during examination or audit review.
          

        


      

    

  










  

    
All fields

    
33-field schema reference

    
Every field in the record schema exists for a specific forensic reason. None are padding. Each maps to at least one named regulatory control.


    

      
FieldType / ValueForensic purpose

      
        
01record_idUUID stringGlobally unique identifier for this artifact.

        
02record_versionsemverSchema version of this record.

        
03evidence_tierTIER-A / B / CEvidence grade: TIER-A, TIER-B or TIER-C.

        
04decision_kindenumWhat kind of decision this record describes.

        
05capture_layerBUSINESS_LAYER / LLM_LAYERWhere in the call stack this was captured.

        
06consequentialbooleanWhether this is a regulated consequential decision.

        
07deployment_modeenumTrust model this artifact was produced under.

        
08created_atRFC 3339 UTCWhen the substrate sealed this record.

        
09principal_identitystringThe actor the substrate recorded as deciding.

        
10action_typestringThe declared class of action.

        
11authorization_token_idUUID stringThe single-use token issued before execution.

        
12input_hashSHA3-256SHA3-256 over the canonical form of the agent's input.

        
13availability_policyenumWhat happens if the evidence service is unreachable.

        
14policy_version_hashSHA3-256Hash of the policy in force at decision time.

        
15model_namestringThe model as identified by the provider.

        
16model_providerstringWho served the model.

        
17model_version_hashSHA3-256Hash pinning the model version actually used.

        
18full_prompt_snapshotstringThe prompt as the model received it.

        
19output_pre_postprocessstringThe model's raw output, before any post-processing.

        
20execution_resultstringThe outcome that was acted on.

        
21causality_chain_hashSHA3-256Binding over this record's provenance envelope.

        
22provenanceenvelopeEnvelope: where this record sits in a workflow.

        
23governance_contextenvelopeEnvelope: who is accountable and under what regime.

        
24execution_contextenvelopeEnvelope: how the decision was actually produced.

        
25tool_call_logarrayEvery tool the agent invoked, in order.

        
26rag_evidence_bundlearrayThe retrieved material the decision drew on.

        
27instrumentation_coveragenumberFraction of the run that was instrumented.

        
28lock_verification_latency_msnumberTime to confirm the WORM lock.

        
29registry_validation_statusenumWhether the agent was in the registry at seal.

        
30sdk_binary_sha3SHA3-256Hash of the SDK binary that produced this record.

        
31sdk_hash_layerenumWhere that SDK hash was established.

        
32signing_key_idhex(64)Fingerprint of the Ed25519 public key that signed this.

        
33signing_attestationhex(128)The Ed25519 signature over the other 32 fields.

      
    

    

      Every field above is in the sample record you can download and verify.