CAIN-42 claim

C42-E37-AUTONOMOUS-EXECUTION-MESH

Evolution 37 (autonomous execution mesh) is a TESTED library: every governed execution runs IDENTITY -> CAPABILITY -> AUTHORITY -> POLICY -> CONTEXT -> EXECUTION ENVIRONMENT -> ACTION -> E8 -> ENFORCEMENT -> OUTCOME -> PROOF -> REASSESSMENT over the real kernel, sealed executor, E8 commit boundary and E34 proof envelope, and leaves a signed receipt whose E8 commit matches the envelope. Moving an execution (node, runtime, model, region, container, credential) is a governed state transition: authority can only shrink, a material change needs a new epoch, continuity tokens cannot exceed existing authority, and risk, spent budget, revocations, transaction limits, evidence, reputation and incident state cannot be reset. UNKNOWN, OBSERVED and MONITORED never become ENFORCED; claims take the weakest boundary. 71 signed execution receipts; 1132/1132 invariants hold; 2720/2720 adversarial scenarios held; mutation 17/17; chaos 16/16 faults contained with 0 false allows; 16 forged objects rejected; 21 tests pass; the clean-room verifier returns INTACT (2627/2627 checks, no CAIN imports).

Last reviewed 2026-10-01

SIMULATED

The claim

Level SIMULATED 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.

category	ARCHITECTURE
status	TESTED
evidence level meaning	adversarial verification
limits	in-process library on one host; declared destinations, regions and clouds are governance records, not deployed nodes; hardware attestation UNKNOWN (no TEE); adapters tested against a reference harness only; cloud targets ARCHITECTURE; the governance quorum is in-process, not the networked PBFT cluster; scale runs are single-host; no customers; PRE-PRODUCTION
verification method	python3 verify_e37.py <bundle dir> (see e37-autonomous-execution-mesh-2026-09-30/REPRODUCTION.md)
revalidate by	2026-12-30T03:20:13Z
claim version	1

Evidence files

Verify this signed claim in your browser

Checks the whole registry's Ed25519 signature against the published evidence-root key, then re-hashes this claim's artifact files. Same algorithm as the standalone verify_claims.py.

From CAIN-42 signed public claims registry.

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