Live independent verification

Verify the route, not the dashboard.

Independent Replay Verification allows anyone to verify a TA-14 replay package without relying on the originating dashboard or operator. The verifier checks preserved package integrity, cryptographic signatures, route identity, receipt dependencies, ledger continuity, execution correspondence, and outcome correspondence against the published standard.

Verify a Replay Package View Published Standard Open API Documentation

Replay verification desk

Upload one replay ZIP package.

Your file is transmitted to the live TA-14 replay-verification endpoint for processing. The package is written to isolated temporary storage, independently checked, and removed when processing ends.

Try the verifier

Sample replay packages

Public sample replay packages are now available. Download the valid package or one of the intentionally altered examples, then upload it directly into the verifier below to compare verified integrity against package tampering, broken ledger continuity, and invalid key correspondence.

Download Valid Replay Package Download Tampered Package Download Broken Ledger Package Download Wrong Signature Package
The valid sample should return VERIFIED. The altered samples are expected to fail for different integrity reasons so visitors can observe the verifier detecting specific forms of replay-package divergence.
No package selected
Verification establishes the integrity and correspondence of preserved records. It does not automatically prove the truth of an unauthenticated external source.
Verification status
Ready

View complete verification response 

          

        

      


      

        

          
Public claim boundary

          
What a successful verification means.

          

            A conforming TA-14 replay package can be verified without trusting
            the originating dashboard or operator. Verification is not legal approval,
            regulatory certification, safety certification, production clearance,
            or a guarantee that every external source was truthful.
          

        


        

          

            
Verification can establish

            

              

                Preserved package integrity
                The included files match the digests declared by the package.
              

              

                Signature correspondence
                The preserved records correspond to the included public keys and signatures.
              

              

                Route and ledger continuity
                The route identity, receipt dependencies, and hash-linked ledger remain coherent.
              

              

                Execution and outcome correspondence
                The preserved execution and outcome correspond to the committed route records.
              

            

          


          

            
Verification does not automatically establish

            

              

                External source truth
                An unauthenticated outside source may still have supplied false information.
              

              

                Legal or regulatory approval
                The verifier is not a court, regulator, licensing body, or certification authority.
              

              

                Universal operational safety
                A verified record does not eliminate every possible real-world failure mode.
              

              

                Production clearance
                Enterprise deployment still requires written scope, security review, and implementation controls.
              

            

          

        


        

          
            Read the Full Replay Standard
          

          
            Explore the Live API
          

          
            Request a TA-14 Review