Offline package verification

Check the evidence before trusting it.

The public sample includes its signed manifest, signer certificate, exact fingerprint, and portable checker. Verification detects changed, missing, or unexpected files without calling VeriTrooper or any network service.

01

Download and extract the entire ZIP

Keep the package structure intact. Do not open only one file from the archive or move the Integrity folder away from the evidence it verifies.

02

Run the included offline checker

On Windows, double-click Integrity\Check this package.bat. The checker is bundled; no VeriTrooper installation, Python runtime, or network connection is required.

If Python is already installed, the transparent alternative is python Integrity\vt_verify.py.

03

Require every core check to report OK

The manifest signature, listed-file hashes, unexpected-file scan, evidence index, and package-consistency checks must pass. Any failure means the package should not be relied on until it is replaced or investigated.

04

Compare the signer fingerprint separately

The checker must display this exact SHA-256 certificate fingerprint:

BE:D1:4C:7B:27:D4:CF:4D:17:76:08:4A:3E:43:60:62:E9:CD:6A:2E:3C:DB:1A:44:C5:3F:15:E1:54:54:A7:39

This website is the separate comparison channel for the downloaded ZIP. A matching fingerprint plus a valid signature establishes that the manifest was signed by the corresponding private key.

05

Understand what the result does—and does not—prove

Integrity verification proves that the listed files match the signed manifest and that the signature validates against the included certificate. The public certificate is self-signed, so identity assurance depends on comparing the fingerprint through this separately published channel. The public sample has no trusted RFC 3161 timestamp and no current approved hash-bound human signoff.

Verification does not prove that every substantive finding is correct, that the evaluated system will behave the same under different conditions, or that any legal or regulatory requirement is satisfied. The published 88.08% result is limited to the recorded 26 August 2026 gpt-5.6-sol Scout run, approved SEC sources, configuration, and 889 scored questions.

Apply the same discipline

Verify one of your own AI workflows.

The 10-business-day sprint produces a scoped evidence package and acceptance record inside your approved boundary.

Request the sprint