CAIN-42 claim

C42-E31-PROOF

every allowed action run through the proof kernel yields a signed GovernanceProof bound to 16 action fields and to four independently signed or hash-chained artifacts (E30 UAR, E28 receipt, E25 receipt, E8 evidence entry); refusals yield signed failure proofs

Last reviewed 2026-10-01

TESTED

The claim

every allowed action run through the proof kernel yields a signed GovernanceProof bound to 16 action fields and to four independently signed or hash-chained artifacts (E30 UAR, E28 receipt, E25 receipt, E8 evidence entry); refusals yield signed failure proofs

Level TESTED is how far the evidence goes: TESTED means a test suite exercised it, LIVE means it was observed on the hosted system. Nothing is claimed beyond its level.

Evidence files

• PROOF_EXAMPLES.json
• TRUST_ANCHORS.json

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).

Limitations of this bundle

• An in-process TESTED library; not hosted; not wired into the gateway, MCPGate or the clusters.
• Witnesses and the dispute engine run in the same process as CAIN: diverse code and separate keys, not separate organizations. No third party has verified any proof.
• CAIN-GIP carriers are in-process reference adapters; no protocol has a network wire implementation. Agent runtimes, model runtimes and workflow engines have no carrier (NOT IMPLEMENTED).
• Trust anchors are published in the same bundle as the proofs: a verifier checks internal consistency against them, not that they belong to a real operator.
• Postconditions are observations by a registered observer key; they say nothing about physical truth.
• World-state version and trajectory are recorded as UNKNOWN: E31 does not bind a world model.
• No trusted time source: validity windows use the issuer's clock; partition behaviour is not addressed.
• Hardware attestation UNKNOWN; zero-knowledge proofs NOT IMPLEMENTED; no external review.
• Scale rows are synthetic and in-process; the 100,000-proof row uses real crypto over synthetic content and the 1,000,000 row is hashing only.
• cain-json-v1 canonicalization is not RFC 8785 JCS.

From CAIN-42 Evolution 31 -- Universal Proof-of-Governance Fabric.