CAIN-42 CAIN StudioEvidence
What we ran on 2026-11-02. Our own testing.
Tampering with the bundle
| Attempt | Verifier result |
|---|---|
| No key pinned | NOT VERIFIED (no trusted key) |
| Correct key pinned | ALL RECORDS VALID |
| Report verdict changed from STUB to REAL | TAMPERED OR INVALID |
| One file's findings removed from findings.json | TAMPERED OR INVALID |
| A different key pinned | TAMPERED OR INVALID |
Is the report about my code? (new)
| Case | audit-code-check.py |
|---|---|
| The audited folder, unchanged (including a file with Windows line endings) | MATCH, exit 0 |
| One line added to one file | DIFFERENT: "changed since the audit: …", exit 1 |
| A new file added | DIFFERENT: "in your folder, not in the audit: …", exit 1 |
| The published sample, downloaded from this site | signature ALL RECORDS VALID; code MATCH |
Tests
tests/test_cain_audit.pyand the product, army and lead suites: 41 passed, including 4 added today (no-review statement and measured accuracy in every report; reviewer notes signed in; reviewer name without notes refused; code check matches and detects changes).python3 -m cain_audit.cli selftest: all six other deliverables produced from synthetic inputs and their bundles verified, 6/6.
FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.