Verifiable evidence surface

Verification

Verify it yourself.

Signed certificates, hash-chained logs, and preserved run archives.

Offline verification

Verify outside the served interface

Requires the repo or installed package.

verify_certificate.py

curl -s https://raw.githubusercontent.com/SDL-HQ/sir-firewall/main/proofs/latest-audit.json | python3 tools/verify_certificate.py -

Expected output

OK: payload_hash matches reconstructed signed payload and signature verifies against key registry spec/pubkeys/key_registry.v1.json entry signing_key_id=default; this proves payload integrity + signature validity only (not policy correctness, model safety, or broader trust guarantees).

How it works

What a verifiable run binds together

Test suite binding

A run binds to a test suite through the suite hash.

Policy binding

A run binds to a policy configuration through the policy hash or version.

Log trail

A run produces an immutable log trail through the final ITGL hash.

Offline-checkable certificate

The published certificate is cryptographically signed and can be verified offline.