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 · public standard · v1 · 2026-11-13

The Proof Standard: verify a record without trusting the vendor.

A dashboard tells you what a vendor says happened. Evidence lets a third party check it. The CAIN-42 Proof Standard defines the difference: a canonical record, a pinned key, a hash chain, and a verifier that imports no CAIN code.

CAN A THIRD PARTY VERIFY THE RECORD OFFLINE, WITHOUT TRUSTING THE ISSUER?

Four conformance levels

L1 · IntegrityCanonical JSON, SHA-256 record hash, Ed25519 signature, verified against a key pinned out of band.
L2 · ChainPrevious-hash continuity and a signed bundle head listing every record in order. No gaps, no reordering.
L3 · AnchorRFC 6962 Merkle root, optionally anchored in a transparency log or quorum certificate. The operator is named.
L4 · Artifact bindingEvery bound artifact's bytes match the digest in the record. The effect is recomputed, not trusted.

Levels are cumulative: L4 implies L1–L3. A verifier reports the highest level it actually checked. L1 is not L4, and neither is a certification.

How to verify

# 1. Take a bundle's own standalone verifier (it imports no CAIN code)
cd evidence/.../signed-sample
python3 verify_offline.py

# 2. Or run the public conformance runner
python3 standard/conformance.py <bundle-dir> --json

# 3. Pin the key yourself, from a source you trust
#    The bundle's own public_key.txt is not trusted until it matches your pin.

Open a real signed sample · Verify in the browser · Pricing and Proof SLA · Verified Record · Machine-readable standard · Read the specification

What this standard proves

It provesIt does not prove
The record is byte-for-byte what was signed.That the record is complete (records can be omitted before signing).
The signature matches the pinned issuer key.That the issuer is independent, or that the quorum is a witness network.
The chain is continuous and the bundle head matches.That the executed action was wise, safe, or legal.
The bound artifacts match their digests.That the tests behind a fix are good, or that a certification exists.

Why this is the buying question

Control planes — agent identity, gateways, runtime policy, dashboards — are converging. All four major vendors can tell you what an agent was allowed to do. The open question is whether their record survives the vendor: can your auditor, insurer, or counterparty re-check it offline, with a key they pinned, without importing the vendor's code?

If the answer is no, you have a dashboard. If the answer is yes, you have evidence. The standard exists so that question has a testable answer.

Status: public draft v1. The record format, verifier behavior, and test vectors are published. The quorum is vendor-operated unless a separate witness network is named. No third-party audit, SOC 2, ISO 27001/42001, or EU AI Act certification is claimed by this page.

Contact: firmeai2026@gmail.com · Everything about CAIN-42 · The Agentic 75