Skip to content
One system, three sites
CAIN-42 CAIN Studio
Get started
Every hosted decision is ordered by a live 4-replica PBFT quorum4-node Byzantine consensus: 3-of-4 Ed25519 quorum certificatesSurvives network partitions and a Byzantine replicaEvery decision signed, hash-chained and verifiable offlineTLA+ model-checked: 7.3M states, 0 violationsDAG dissemination anchored and ordered by PBFTA tool call runs only with a quorum-committed authorizationAgent authority is a short-lived, single-use leaseAn agent cannot grant itself a new capabilityA hosted governor for L5 autonomous systemsA caught attacker loses autonomy; risk-weighted decisionsPhysical actions bind nine digests behind a single-use permitTwo replicas' storage lost at once: 0 decisions lostLive rollback and forward under traffic, no quarantinesThe deployed image rebuilds bit-for-bit4 replicas on 4 servers across 4 regionsConsensus live across three regions over WireGuardLive cluster — watch and verify nowProof: what is live nowVerify every claim yourselfVerification CenterDownload the evidence packSBOMFormal models (TLA+)Test reportFault-injection proofHosted-consensus proofMCPGate enforcement proofL5 hosted-evolution proofSpatial & physical proofStorage-loss drillRollback drillFour-server clusterChangelogLab

Don't trust CAIN-42. Verify CAIN-42.

Here are the receipts

Every public claim about CAIN-42 is listed below with its evidence. Your browser downloads each file, recomputes its fingerprint (SHA-256) and checks the signature itself; nothing on this page asks our servers whether the evidence is valid. A claim that is only tested, or only claimed, says so.

Check the claimsDownload the evidence packVerify without this page

What exists right now

Loaded from the published, signed files as this page opens.

loading…

How to read a claim

REPRODUCIBLE

Verified, and the verifier is published: you can run the same check yourself and get the same answer.

TESTED

Automated tests pass, but no independent check has been published. A failed result stays visible as a failure.

CLAIMED or SUPERSEDED

Claimed: said, not yet shown. Superseded: replaced by a newer claim and kept for history. Nothing here is verified by a third party; no one has reviewed CAIN-42 independently yet.

Every signed claim

Pick a claim and follow it: claim, evidence, hash, signature, test, source, verifier.

Verify without this page

For engineers, auditors and AI agents. Python 3 and cryptography; the verifiers import nothing from CAIN-42.

curl -O https://clawx.click/evidence/proof-fabric/verify_proof_fabric.py.txt && mv verify_proof_fabric.py.txt verify_proof_fabric.py
python3 verify_proof_fabric.py https://clawx.click/evidence/proof-fabric/ --claims --text
python3 verify_proof_fabric.py --pack https://clawx.click/evidence/proof-fabric/CAIN42_EVIDENCE_PACK.zip
curl -s https://cainstudio.online/api/v1/proof            # machine-readable index (a convenience, not a verifier)

What they recompute: the claims registry signature, every claim's artifact hash on all three sites, the build and deployment manifests, the test counts against the published JUnit XML, and every public test vector with independent code. The ten-step workflow is inside the evidence pack (VERIFY_WORKFLOW.md). Machine-readable: proof-fabric manifest · test vectors · provenance graph · SBOM · signed index.

Found something wrong? Tell us

A verification error, an inconsistent bundle, a claim the evidence does not support, or a result you could not reproduce: email security@cainstudio.online with the claim id, the file and what you ran. Evidence problems are handled like security reports under the disclosure policy (safe harbour, response targets). Please test against the published files and the public Lab, not by degrading the live service; there is no bug bounty.