Proof, not promises.
11/11 publishes the exact cryptographic primitives used at every layer of the control plane. Reviewers do not have to guess. Each public claim is paired with a way to verify it, or marked as roadmap.
This is a live demonstration of signed evidence roots and chained audit lineage. Independent security testing is in progress.
The cryptography is named, not implied
Primitives, stated at every layer.
The control plane evidence state is chained with SHA-512. The audit and lineage chain is chained with SHA3-512 and BLAKE2b-512, each verified independently by the reference verifier. SDK receipts are chained with SHA3-512 and Ed25519 signed, and they verify on your own machine. These are separate structures with separate threat models. This page names each one rather than averaging them into a single line.
$ curl -s https://control.11aiblockchain.com/v1/public/evidence \
| jq '{decision, execution_id, ea11_evidence_root,
signatures: .hybrid_signature_envelope
| {ed25519: .ed25519.status, ml_dsa: .ml_dsa.status,
sphincs_plus: .sphincs_plus.status}}'
{
"decision": "APPROVED",
"execution_id": "EX-773FCDB1",
"ea11_evidence_root": "3942d2e38c34296bd8a6290713a4c405b4b15f1ee83c25b44dbd551d4d24078c560d3a481ebc717964d0690dacde18fc069abf25fdc0866d2650fb36f43c1984",
"signatures": {
"ed25519": "SIGNED",
"ml_dsa": "VALID",
"sphincs_plus": "VALID"
}
}
Read the projection
Every field, explained.
The pipeline projects a fixed set of fields from the live record; the terminal shows one example run, retrieved 6 August 2026. execution_id and ea11_evidence_root differ per record; decision and the three signature statuses are what to check.
- ✓ decision: the governed verdict, APPROVED or DENY.
- ✓ execution_id: the identifier of the governed execution.
- ✓ ea11_evidence_root: the 512-bit root the signatures commit to.
- ✓ signatures: the status of each signature over that root, Ed25519 and post-quantum ML-DSA-87 and SLH-DSA-SHA2-128f.
EA-11 Evidence State · v2.2 Live
Deterministic, Merkle-rooted execution evidence.
11/11 has upgraded from single proof-hash evidence to deterministic EA-11 Evidence State v2.2. Governed executions that carry EA-11 evidence bind Decision Hash, Artifact Hash, Execution Hash, Audit Hash, and Lineage Root into a Merkle-rooted evidence state with inclusion proof verification and fail-closed tamper detection. Seven records on the public ledger are marked evidence_state MISSING and carry no envelope. This strengthens third-party verification, audit reconstruction, certification readiness, evidence lineage integrity, and governed execution trust.
EA-11 Evidence State v2.2 is live: deterministic component hashes, Merkle-rooted execution evidence, inclusion proof verification, fail-closed tamper detection, real post-quantum signatures, SDK verification, and Ed25519 JWKS discovery.
- ✓ Decision Hash
- ✓ Artifact Hash
- ✓ Execution Hash
- ✓ Audit Hash
- ✓ Lineage Root
- ✓ EA-11 Merkle Root
- ✓ EA-11 Evidence Root
- ✓ Merkle Inclusion Proofs
- ✓ Fail-Closed Evidence Verification
- ✓ Tamper Detection
- ✓ Formal Specification
EA-11 Evidence Verification
Merkle inclusion proof verification implemented; SDK tests passing.
JWKS Origin Endpoint Live
Gateway running with Ed25519 public verification discovery active.
PQ Enforcement Required
ML-DSA-87 and SLH-DSA-SHA2-128f enabled. Post-quantum verification VERIFIED as reported by the signer. Independently verified in the reference path: Ed25519.
- ✓ EA11_EVIDENCE_STATE_V2_2
- ✓ Real ML-DSA-87 Enabled
- ✓ Real SLH-DSA-SHA2-128f Enabled
- ✓ PQ Verification VERIFIED
- ✓ PQ Enforcement REQUIRED
- ✓ 130 of 144 records carried a recomputable evidence root on 9 October 2026
- ✓ Fail-Closed Runtime Enabled
- ✓ PQ Enforcement: REQUIRED
- ✓ PQ Verification: VERIFIED
- ✓ ML-DSA-87: VALID
- ✓ SLH-DSA-SHA2-128f: VALID
- ✓ Evidence State: EA11_EVIDENCE_STATE_V2_2
- ✓ 130 of 144 records carried a recomputable evidence root on 9 October 2026
ML-DSA-87 and SLH-DSA-SHA2-128f status is as reported by the signer. Independently verified in the reference verification path: Ed25519.
The public ledger held 144 records on 9 October 2026. 128 of those are canary records, written by a scheduled health check, and 16 are operational. The record_type field reports which is which, and the count on this page is the full ledger, not a count of customer traffic. We publish the split because the endpoint publishes it.
SDK · Open source · live on npm
Verify a decision, then govern your own agent.
@11ai/execution-governance is the single developer surface for the 11/11 control plane. One package, one integration, two capabilities. The SDK requests and verifies. The control plane holds the keys and signs. Governance sits on the action, not the model, so one integration covers OpenAI, Anthropic, Grok, and your own custom agents alike. Vendor-neutral by construction.
Check any decision yourself
Verify governance decisions against the public JWKS and proof endpoint. The same public verification surface this site already exposes, now callable from your own code.
Put your agent behind the boundary
Wrap your own agent's actions in pre-execution authorization and fail-closed enforcement, with a signed proof of every decision. The fuller use of the same SDK.
Vendor-neutral by construction
It governs the action, not the model. One integration covers every agent you run.
OpenAI
Anthropic
Grok
Custom agents
How the govern path works
Every action your agent takes is authorized before it can run, and proven after.
Agent builds a request
SDK signs and sends it
Signed allow or deny
Verify against public JWKS
Proceed, or never run
- ✓ Your agent builds an action request.
- ✓ The SDK signs the request and sends it to the control plane.
- ✓ The control plane returns a signed allow or deny decision.
- ✓ The SDK verifies that signature against the public JWKS.
- ✓ Allowed actions proceed. Denied actions never run. Every decision is recorded.
The SDK is open source and installable from npm today: npm install @11ai/execution-governance (0.4.2, Apache-2.0). It is early and moving fast, so treat v0 as a preview, but you can install it, run npx eg-demo, and verify a real signed decision yourself right now. The demo's receipts also verify offline on your own machine with npx eg-verify, with no network. Full details on the SDK page.
Execution Governance™ · Governed Execution™ · EA-11™ · Execution Arithmetic™ · Execution Evidence State™ · Patent Pending
Published & citable
The doctrine is on the public record.
11/11 publishes its execution governance architecture as formal, DOI-registered reports through the 11/11 AI Research Division. Each is permanently archived, openly licensed, and independently citable. This is proof you can footnote.
11/11 Execution Governance Architecture: A Fail-Closed Execution Governance Layer for Regulated AI and Compute Infrastructure
DOI 10.5281/zenodo.20252295 Read on Zenodo → Report / Architecture11/11 AI: A Deterministic Execution Authority Architecture for Governed AI, Data, and Autonomous Systems
DOI 10.5281/zenodo.20252639 Read on Zenodo → Standard / CharterRFC-EG-0001: Charter of the RFC-EG (Request for Comments, Execution Governance) Series
DOI 10.5281/zenodo.20260882 Read on Zenodo →Reference verifier & standards track
Verify a governed decision against the reference implementation.
Open-source verifier: clone and run in 30 seconds 
RFC-EG-0010 Lineage Verifier
Open on GitHub → Conformance profiles11/11 Governance Profiles
Open on GitHub → Archive11/11 AI Research Division: full corpus
Browse all records →Verification before runtime. Enforcement during runtime. Proof after runtime. Copyright © 2026 11 AI Blockchain Developments Land and IP Trust. Execution Governance™, Governed Execution™, EA-11™, Execution Arithmetic™ , Execution Evidence State™ , Patent Pending.