Platform

Production beta — proofs are signed and publicly verifiable today; production execution unlock in progress

Proof System

An Autonomous Execution Proof is the tamper-evident, replay-verifiable record of a single autonomous action — what ran, under which policy version, under whose authority, and with what cryptographic integrity.

How it works

Proofs are generated by the Intentrax Assurance Engine, not by this website. What you read here is the model; the proof itself is signed and independently checkable.

Open public verification
An append-only, tamper-evident registryEach record's canonicalized fields hash into a proof_hash, and every record chains to the previous one — so editing an earlier proof visibly breaks every later link.

Verification Handoff

Open the public verifier from the product page

Every verification result is read from the proof registry — this site never generates one.

What this page provides

What a proof captures

Each proof binds one execution to a verifiable record: the canonical event, the policy version that governed it, the authority that permitted it, and a signature that seals it.

  • Canonical execution event
  • Policy version and authority
  • Issuer signature

Why it holds up

Every integrity-relevant field is canonicalized and hashed into a proof hash, then signed. Any later change breaks the hash and invalidates the signature.

  • Canonicalized and hashed
  • Tamper-evident
  • Independent of your logs

What you can do with it

Export a proof as JSON or a human-readable PDF companion, hand it to an auditor or counterparty, and let them verify it themselves.

  • JSON and aep-json export
  • PDF companion
  • Independent verification

Recommended next steps

Verify a proof

Continue to the review path when your team is ready to map an assurance pilot.

Verify a proof

Start with an Architectural Review

Intentrax will review your context and prepare a recommended assurance path.

Request Architectural Review