Execution Governance Developer Docs

Documentation

Introduction

11/11 Execution Governance is sovereign runtime infrastructure that decides whether an AI, agent, or autonomous system is allowed to act, before the action reaches the real world. Authorization is evaluated before execution, enforced during runtime, and proven after the fact.

Quickstart

The 11/11 Execution Governance SDK is in private beta. Request access at contact and we will provision your install package and credentials. Once provisioned, create a client and submit a governed execution request:

import { createClient } from "@1111-ai/execution-governance-sdk";

const client = createClient({
  apiKey: process.env.EG_API_KEY,
  baseUrl: "https://control.11aiblockchain.com"
});

const result = await client.controlFlow({
  subject: "agent:demo", action: "execute",
  resource: "workflow:example",
  context: { environment: "production" }
});
console.log(result.status);

Authentication

Requests are authenticated with an API key supplied at client creation. Keys are provided through onboarding and must be stored as secrets, never committed to source or embedded in client bundles. Rotate keys regularly and on suspected exposure.

Execution Governance

Execution Governance is the pre-execution authorization layer. Every action is bound to an identity (subject), an operation (action), a target (resource), and an environment (context), then evaluated against the active policy set before it is permitted to run. The result is a governance decision and, when permitted, an authorization artifact that gates downstream execution. Internal policy-engine logic is not exposed.

Governed Execution

Governed Execution is runtime enforcement. An action proceeds only when a valid authorization artifact is present; without it, execution is stopped. Enforcement is fail-closed: the default outcome in the absence of explicit authorization is denial. There is no path around the control plane.

EA-11 Execution Arithmetic

EA-11 produces a deterministic, Merkle-rooted evidence state for every governed execution. Each decision is reduced to a set of component hashes that can be independently verified. The underlying arithmetic and internal math are proprietary and are not published.

Fail-Closed Governance

Fail-closed means the default is deny. If authorization is missing, invalid, or cannot be evaluated, the action does not proceed.

SDK Overview

The Execution Governance SDK provides a typed client for governed execution, authorization-artifact verification, and proof verification against the public control plane. SDK is live and validated end-to-end against the production control plane.

JavaScript SDK

Install and use the JavaScript / TypeScript client.

const verified = await client.verifyArtifact({
  artifactHash: "sha3-512:example",
  proofHash: "sha3-512:example"
});

API Overview

Public infrastructure surfaces. Endpoints beyond those listed are described as conceptual interface documentation only.

Authorization API

The authorization flow evaluates a request and returns a governance decision and, when permitted, a proof artifact.

Request → Policy Evaluation → Governance Decision → Execution Permission → Proof Artifact

Proof API

Each governed execution can be verified against the public proof surface. Both APPROVED and DENIED decisions are signed and recorded. Human-readable proof is available at the public Proof Viewer.

Health API

The public health endpoint reports infrastructure status.

GET https://control.11aiblockchain.com/health

Financial Profile

Governed execution for financial infrastructure. High-value transactions and settlement actions are authorized before they execute, with per-tenant isolation and signed, verifiable evidence for every decision. Direct payment-rail and stablecoin integrations are on the roadmap.

Healthcare Profile

Governed execution for clinical and healthcare AI. HIPAA-aligned decision boundaries are enforced before patient-impacting actions occur, with immutable audit lineage and fail-closed operational controls.

Defense Profile

Governed execution for sovereign, regulated, and mission-critical environments. Fail-closed authorization gates every action with tenant-scoped isolation, cryptographic execution controls, and independently verifiable evidence for audit and oversight.

Conformance Overview

Conformance profiles describe requirement sets for governed execution across sectors, mapped to recognized frameworks where applicable.

Resources

Public surfaces, the main site, and contact.