The sample files match the signed record. The signer matches the sample key in this checker.
What still needs a check
A pass does not prove the facts are true. It does not mean your AI tool meets every rule.
Show test cases and technical details
Published fixture suite
See why each check stops.
Choices 1 to 3 of 8. You can come back to each choice.
The signed v2 commitment binds the manifest, package metadata, record history, and identified sample trust material. The public key is pinned in this verifier. A package cannot supply its own trusted key.
This fictional signing proof is not RFC 3161, independent proof of time, evidence of true facts, a compliance determination, or a legal-admissibility decision. Older v1 samples remain unverified because their signed proof did not bind the manifest.
Offline command
Run this check on another machine.
Algorithm briard-package-integrity-v2. Requires Node.js 22 or newer. Save the sample and both verifier files in one folder, then run the command there. No package data is sent.
Briard checks normal review downloads before saving them. For a later file check, get the expected SHA-256 from the authenticated download response through your workspace administrator. The separate checker compares file bytes with that supplied check. It does not verify a signature or replace Briard Alert & Response Console (BARC) custody verification.
