CAIN-42 claim

C42-E30-KERNEL

one action path (kernel -> E28 -> E25 -> E8) that checks autonomy state, level, budget, containment, environment, perception, memory and intent before authorizing, and a signed universal action receipt binding a 20-field action digest for every action, allowed or refused

Last reviewed 2026-10-01

TESTED

The claim

one action path (kernel -> E28 -> E25 -> E8) that checks autonomy state, level, budget, containment, environment, perception, memory and intent before authorizing, and a signed universal action receipt binding a 20-field action digest for every action, allowed or refused

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

• E2E_ARTIFACTS.json
• INVARIANTS.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 integration library in one process; not hosted; not wired into the gateway, MCPGate or the clusters.
• Governance coverage outside the E25/E8 boundary is UNCONTROLLED or UNKNOWN (see COVERAGE_MAP.json); robots, vehicles, laboratories and physical actuators are UNENFORCED -- CAIN refuses to act there, it does not govern them.
• Perception VERIFIED means two independent registered sensor keys agreed; it says nothing about the physical truth of the reading.
• Injection detection in memory, perception and intent is a marker list; recall against real attacks is UNKNOWN.
• The self-improvement firewall governs the process; it cannot tell whether a promoted change is actually better or safe beyond the recorded stage evidence.
• Grid scenarios are distinct inputs over shared defences; the mutation self-test shows which defences they exercise.
• The TypeScript SDK is a verifier; agent-side TypeScript integration is not built.
• The research engine and frontier lab are registers only; no automated research feed runs.
• Scale rows are synthetic and in-process; the 100,000 row is a virtual model without signatures or E8.
• Hardware attestation UNKNOWN; zero-knowledge proofs NOT IMPLEMENTED; no external review.

From CAIN-42 Evolution 30 -- Governed Machine Autonomy Fabric.