Verify the evidence on your own laptop.
Compliance evidence is often reviewed inside the product that assembled it. ControlFrame also exports a portable bundle that a reviewer can inspect with a local, self-contained verifier. The public download is a labeled synthetic reference: it demonstrates integrity checks and tamper detection, not production collection or certification.
Open the downloaded HTML from disk, then select the bundle. That is the no-callback verification path. A hosted checker can be convenient, but it is not an independent or neutral trust authority.
Save the local verifier
Download the single-file verifier below. It is plain HTML with inline JavaScript and zero dependencies — no build step, network request, or analytics call is required to run it from disk.
Download the synthetic bundle
The reference bundle (.json) carries illustrative controls and evidence, a decision passport, a chain-of-custody manifest, and a governed-receipt/v1 in one file. It is not a customer record or audit attestation.
Recompute and inspect
Open the verifier from disk and drag in the bundle. It re-derives covered hashes, checks the embedded Ed25519 signatures, and reports either an intact result or the section that failed validation.
Integrity is portable. Provenance still matters.
The local file independently recomputes the bundle's covered hashes and signature checks without relying on a live application session. Those checks establish integrity and signer possession; the reviewer still evaluates key provenance, evidence sufficiency, and the final assurance conclusion.
Local verification, no callback
When saved and opened from disk, the verifier performs its checks in the browser without calling a ControlFrame server. It recomputes covered hashes and checks signatures against the public key carried with the record; reviewers must still establish that key's provenance.
Tamper is visible to the byte
Flip one character in any sealed section — a control, evidence row, decision record, or the receipt body — and the recomputed hash diverges: the verdict goes red and points at the failing section. Unsealed envelope labels sit outside the manifest and are not covered.
Designed for disconnected review
Once the HTML and bundle are saved locally, a reviewer can run the integrity checks without network access or a live application session. Evidence sufficiency and final attestation remain the reviewer's responsibility.
Build your own bundle, then prove it offline.
The auditor evidence package surface assembles a bundle for any framework over a synthetic profile. Export it, then drop it onto the offline verifier — the round-trip is the proof.