CAIN Proof Center

Real 4-node PBFT (Byzantine, f=1) consensus cluster: live-captured Ed25519 quorum certificates, a zero-import independent verifier you can download and run yourself, and the full root-cause writeup of a real bug found and fixed live during CAIN 35.0. Nothing here requires trusting this server.

A cryptographically hash-chained, Merkle-sealed evidence log built from real live PBFT commits, plus a machine-readable connectivity forensics report explaining exactly why this evidence is not yet reachable via the literal cainstudio.online / mcpgate.online domains -- including a real unauthenticated-firewall-exposure finding this session discovered while investigating that gap. Nothing here is claimed complete: see the bundle's own honest_scope_note.

CAIN does not become the bank -- it is the trust fabric that makes autonomous economic action verifiable. Every economic action requires a real agent identity, a real spend-capped delegation, and a real budget reservation before a (currently simulated-only) execution can occur. This session found and fixed two real, live bugs in the pre-existing delegation and budget engines this pipeline depends on -- see the bundle for the exact root causes and fixes.

CAIN 39 closed two gaps CAIN 38 found but left open: delegation tokens are now actually Ed25519-signed and verified (not just hashed), and revoking an agent's identity in either of CAIN's two identity registries now blocks its economic authority. It also adds a real, replayable escrow/conditional-settlement state machine. The other ~45 of the mission's 50 phases (agent discovery, negotiation, marketplace, MCP/A2A trust fabric, 100k-scenario campaigns, SDKs) were NOT attempted -- see the bundle's own limitations file.

The new AgentOrganization primitive: a constitution that is immutable by construction (a frozen dataclass, not a policy note), team formation that requires a cryptographically SIGNED authorization for every member added, and collective decisions where dissent is always preserved in the evidence, win or lose. One real 2-agent, 8-state, end-to-end lifecycle is published below. The other ~45 of the mission's 50 phases (Byzantine agent consensus, emergent-behavior detection, federation, digital twins, million-scenario campaigns) were NOT attempted.

A UniversalAgentProof composes evidence from independent CAIN subsystems (here: a fresh economic decision and an existing organization decision) into one signed object, verified with a per-sub-proof breakdown proving -- not just claiming -- that tampering one referenced subsystem never silently invalidates another. This session's own tamper-isolation test caught a real bug in the first draft of the verifier (it compared a stored hash string instead of recomputing one independently) before publishing -- documented, not hidden. A public POST /api/v1/universal-proof/verify endpoint lets anyone submit a proof and get an independently-computed verdict, never "trusted" merely because CAIN produced it.

Closes gaps CAIN 37-41 repeatedly flagged NOT ATTEMPTED: a real MCP server (built on the official SDK) behind a real DISCOVER->TRUST->AUTHORIZE->EXECUTE gate, a real A2A agent behind the same 4-gate model, a signed supply-chain provenance manifest independently recomputable from a repo checkout, an identity-registry reconciliation fix, and a real (20-agent) demonstration that majority-vote collusion can be defeated by a quorum threshold CAIN already has. This is NOT a claim that CAIN has been renamed or that the mission's full scope is complete -- see CAIN42_MIGRATION_PLAN.md for the honest gap list that remains.

The first real, end-to-end flow tying ARD (Agentic Resource Discovery) catalog discovery, real MCP tool execution, real economic settlement, and evidence composition together in ONE orchestrated call -- with each stage's own independent authorization check still intact (ARD catalog trust never substitutes for the MCP gate's own re-verification; a successful tool call never substitutes for economic authorization). Plus a real 100-agent test exercising the actual identity+signature+add_member onboarding pipeline at scale, including Sybil-vote exclusion.

CAIN is a closed-loop runtime trust control system. It governs consequential autonomous actions before, during, and after execution — combining identity, authority, policy, risk, trajectory, enforcement, execution evidence, and continuous trust-state updates.

Every proof bundle below contains real, mathematically verified cryptographic evidence, Ed25519 signatures, and RFC-3161 Merkle WORM hashes: