CAIN-42 CAIN Studio
CAIN-42 Proto-VAGI is the infrastructure governor of AGI. Early, measured signs of intelligence; every governed action comes with a signed receipt. Evidence · Auditor index · VAGI Agents · not yet AGI
CAIN-42 · Reproduce

Reproduce the evidence.
No CAIN code required.

Download the signed E82 bundle, run the standalone verifier, and get the same result we did. 55 checks, one Merkle root, zero CAIN imports. Then sign an external attestation so the claim ledger can move from L1 to L2. You can be the first named external reproduction.

55/55 CHECKS10/10 TAMPER MUTATIONS REJECTED240 FILESMERKLE 63868034…EXTERNAL REPRODUCTIONS: 0THIRD-PARTY AUDIT: NOT PERFORMED

0. Check the download in your browser — no install

ZIP integrity check

After downloading the ZIP, select it here. Your browser computes SHA-256 locally; nothing is uploaded. Expected: 484f4dfe54cc83de618f3ff420427afacacb5a3201ae3309590435336e63096f.

Choose CAIN42_E82_EVIDENCE_BUNDLE.zip…

1. Download

Evidence bundle

240 files, ~1.1 MB ZIP. Raw rows, model ledger, recovery records, gates, Merkle root, signature.

⬇ bundle.zipSHA256SUMS

Standalone verifier

Python standard library + cryptography. No CAIN module. Recomputes the headline numbers from raw rows.

⬇ verify_e82_offline.py

Manifest + key

The detached Ed25519 signature and public key. The key is self-generated; there is no independent witness yet.

MANIFEST.json.sigkey

Node.js verifier

No Python. Node 20+ built-ins only. 40 checks, same Merkle root. A second-language implementation.

⬇ verify_e82_node.mjsresult

Go verifier

Standard library only. 30 checks. No Python or Node.

⬇ verify_e82.goresultstatus.json

CI template

Drop this workflow into GitHub Actions and verify the bundle on every run.

verify-cain42.yml

Attestation kit

Sign a small JSON that records your environment, commands and result. This is what makes it external.

templateschemaattestation verifier
QR code to this reproduction page

Share it on a phone

Scan to open this page. The badge links to the verifier, not a certification.

CAIN-42 E82 55/55 checks, verify yourself

2. Run it

Expected SHA-256 for the ZIP: 484f4dfe54cc83de618f3ff420427afacacb5a3201ae3309590435336e63096f

Linux · macOS · WSL

sha256sum CAIN42_E82_EVIDENCE_BUNDLE.zip
# expected: 484f4dfe54cc83de618f3ff420427afacacb5a3201ae3309590435336e63096f
unzip CAIN42_E82_EVIDENCE_BUNDLE.zip
python3 -m pip install cryptography   # or use a venv if your Python is externally managed
python3 verify_e82_offline.py bundle | tee verifier-output.json

Windows PowerShell

Get-FileHash .\CAIN42_E82_EVIDENCE_BUNDLE.zip -Algorithm SHA256
Expand-Archive .\CAIN42_E82_EVIDENCE_BUNDLE.zip -DestinationPath .
py -3 -m pip install cryptography
py -3 .\verify_e82_offline.py .\bundle | Tee-Object verifier-output.json

One command (Linux / macOS)

curl -fsSLO https://cainstudio.online/proof/bundle/evolution-82-vertical-agi-2026-11-17/verify_live.sh
sh verify_live.sh

One command (Windows PowerShell)

Invoke-WebRequest https://cainstudio.online/proof/bundle/evolution-82-vertical-agi-2026-11-17/verify_live.ps1 -OutFile verify_live.ps1
.\verify_live.ps1

Go (standard library only)

unzip -q CAIN42_E82_EVIDENCE_BUNDLE.zip
go run verify_e82.go bundle
# expected: ok=true, 30/30 checks, same Merkle root

Node.js (no Python)

unzip -q CAIN42_E82_EVIDENCE_BUNDLE.zip
node verify_e82_node.mjs bundle
# expected: ok=true, 40/40 checks, same Merkle root

Clean container (different filesystem and Python)

docker build -f Dockerfile.verify -t cain-e82-verify .
docker run --rm cain-e82-verify

⬇ Dockerfile.verify⬇ verify.sh⬇ verify.ps1

3. What you should see

CheckExpected
Result"ok": true
Checks55/55
Merkle root63868034b46e901f2cec392cd25c22ab947516e594543e02155857a9c31c5ac9
SignatureEd25519 over the canonical manifest; public key 11Rdogd3q/uwkrCwHVRqodV5S6/VnLvhlopoS+1vaMo=
Recomputedbenchmark accuracy, collaboration accuracy, capacity calls, cross-host prefixes, gate counts, call counts
Tampermodified, removed, added, reordered, truncated and re-signed mutations are rejected

4. Clean-room results already recorded

We ran the verifier in python:3.11-slim, 3.12-slim, 3.13-slim and on the development replica in a fresh directory. Every run returned 55/55 and the same Merkle root. These are our runs — the external attestation is still yours to sign.

clean_room_reproduction.jsonDockerfile.verify

4b. Assurance beyond hashes

Integrity is not the whole claim. These are the adversarial and formal checks behind the boundary:

5. Verify the external time anchor

The manifest hash is timestamped by FreeTSA under RFC 3161 at 2026-11-17T04:27:10Z (serial 0x0A149C12). This proves the manifest existed at that time. It does not prove correctness and is not an audit.

sh verify_timestamp.sh
# expected: Verification: OK

⬇ MANIFEST.tsrtsa_verification.jsonverify_timestamp.sh

6. Record the external reproduction

Fill the template, sign canonical JSON with your own Ed25519 key, verify it with our standalone attestation verifier, and email the signed JSON. We publish valid attestations — including failures — and update the claim ledger.

python3 verify_external_attestation.py attestation.signed.json
# expected: ok=true, evidence_class=EXTERNAL_ATTESTATION

⬇ attestation templateHow to sign itSubmit by email

What this does and does not prove. It proves that the bundle you downloaded is the bundle we signed, that its 55 checks pass on your machine, and that the headline numbers are recomputed from the raw rows. It does not prove the evidence is complete, that the benchmark is generally representative, or that a third party has audited CAIN-42. Those are separate claims with separate targets in the claim ledger.

Third-party audit: NOT PERFORMED · Independent witness cosignatures: 0 · External reproductions recorded: 0 · Target 2027: 3+. This page is a verification kit, not a certification.