CAIN-42 CAIN StudioCAIN-42 evidence library
CAIN-42 Evolution 34 -- Proof-Carrying Machine Agency
Evidence bundle for evolution E34: 8 claims, 627 of 627 invariants held.
Last reviewed 2026-10-01
Browse the raw bundle · How to reproduce it · SHA-256 manifest
Claims (8)
| Claim | Level |
|---|---|
| C42-E34-ENVELOPE: every executed governed operation yields one signed GovernanceProofEnvelope binding identity, capability, delegation, authority, policy, evidence, risk, decision, the E8 commit, the enforcement boundary, execution and outcome, with its unknowns listed | TESTED |
| C42-E34-ENFORCEMENT: an enforcement proof distinguishes decision, authorization, commit, enforcement, execution and observed outcome; enforcement is never inferred from policy or intent | TESTED |
| C42-E34-RECEIPTS: receipts form a tamper-evident chain, never grant authority, and a ProofCarryingAction is refused as authority | TESTED |
| C42-E34-DELEGATION: delegation proves attenuation link by link and never flows back up | TESTED |
| C42-E34-EXCHANGE: governance proofs can be selectively disclosed to another party with salted per-field commitments and RFC 6962 Merkle inclusion, without exposing the rest | TESTED |
| C42-E34-BENCH: 2664 of 2664 scenarios across 32 categories held; 629 of 629 invariants; mutation 12 of 12 | TESTED |
| C42-E34-CLEANROOM: an independent verifier that imports none of CAIN re-derives every envelope, receipt, primitive and proof and rejects every crafted forgery | TESTED |
| C42-E34-HONEST-SCOPE: the governance cloud is NOT DEPLOYED; zero-knowledge proofs are not implemented; protocols are reference adapters; physical systems are refused, not governed | TESTED |
Invariants: 627 of 627 held
Rules the code must never break, each checked across many scenarios. See all 627 on one page.
| Niche | Held |
|---|---|
| Benchmarks, coverage & performance | 195 of 195 |
| Evidence, receipts & proofs | 124 of 124 |
| Policy, law & governance | 93 of 93 |
| Transactions, markets & economics | 43 of 43 |
| Tools, MCP, protocols & adapters | 40 of 40 |
| Trust & reputation | 39 of 39 |
| Attacks, threats & containment | 31 of 31 |
| Identity, authority & delegation | 20 of 20 |
| Memory, data & privacy | 16 of 16 |
| Supply chain, registry & lifecycle | 14 of 14 |
| Prediction, world models & simulation | 12 of 12 |
Verify it in your browser
Your browser downloads the bundle's SHA256SUMS manifest and the file(s) behind this page, hashes them with SHA-256 locally (WebCrypto), and compares. A match shows the record you are reading is the published one; it does not by itself prove who published it (see the signed claims registry and the bundle verifier for that).
Known limitations
- An in-process TESTED library; not hosted. The proof fabric composes E25/E28/E30/E31/E33 but is not wired into the hosted gateway, MCPGate or the clusters.
- Zero-knowledge proofs are NOT implemented (RESEARCH/PLANNED). Selective disclosure uses salted hash commitments and RFC 6962 Merkle inclusion proofs, not ZK.
- Interchange protocols are E25 reference adapters; no network wire implementation of MCP/A2A/gRPC exists here. Physical and vehicle/robot boundaries are refused, not governed.
- The Proof Exchange, federation, marketplace and governance cloud are library surfaces only: no external counterparty, no federation peer and no deployed cloud exist.
- Conformance G0-G7 is an internal profile; G7 requires a separate organization and is never claimed locally. This is not a regulatory certification.
- Transaction proofs sit on E29 synthetic units; there is no payment rail or real money movement.
- The machine reputation vector and governability index are evidence views; they never collapse into a score and never mint authority.
- Mutation self-testing runs each mutant against the bench subset that exercises the mutated component.
- Scale rows reuse the E33 synthetic in-process benchmark; the proof layer adds a 50-sample latency row only.
- No third party has independently verified anything in this bundle.
The bundle's own README
CAIN-42 Evolution 34 -- Proof-Carrying Machine Agency#
Every consequential governed operation can carry one signed, chained GovernanceProofEnvelope that states: this action was governed under these verified conditions -- and which parts are UNKNOWN, UNCONTROLLED, UNVERIFIED, SIMULATED or outside the boundary. A proof never creates authority. Verify with verify_e34.py.txt (see REPRODUCTION.md). Status: TESTED library, pre-production.
Try CAIN-42 on your own agents
Create a free account and every new account starts with a 7-day trial of the full platform. Or try the sandbox first, with no account at all.
Create a free account → · Try the sandbox · See the whole ecosystem