Compatibility

HELM AI Kernel compatibility is the retained public surface that maps to code, examples, tests, or canonical docs. Historical experiments are not supported unless they appear in the source-backed tables below.

Audience

This page is for developers and operators deciding whether HELM AI Kernel supports their operating system, SDK language, framework helper, policy language, deployment target, or verification path today.

Outcome

After this page you should know which surfaces are supported, example-only, or outside HELM AI Kernel; which source paths prove each claim; and which validation commands must pass before a compatibility claim changes.

Surface Map

flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        Kernel["Go kernel and CLI"]
        API["HTTP API and proxy"]
        Console["self-hostable HELM AI Kernel Console"]
        SDKs["SDKs and adapters"]
        Starters["provider starters"]
        Deploy["Docker and Kubernetes"]
    end

    subgraph Evaluation["2. Evaluation & Policy Plane"]
        Policy["CEL, Rego, Cedar bundles"]
    end

    %% Operational Flow Edges
    Kernel --> API
    API --> Console
    API --> SDKs
    SDKs --> Starters
    Kernel --> Policy
    Policy --> Deploy

    %% Premium Styling Rules
    style Policy fill:#2d3748,stroke:#4a5568,stroke-width:2px,color:#fff

flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        Kernel["Go kernel and CLI"]
        API["HTTP API and proxy"]
        Console["self-hostable HELM AI Kernel Console"]
        SDKs["SDKs and adapters"]
        Starters["provider starters"]
        Deploy["Docker and Kubernetes"]
    end

    subgraph Evaluation["2. Evaluation & Policy Plane"]
        Policy["CEL, Rego, Cedar bundles"]
    end

    %% Operational Flow Edges
    Kernel --> API
    API --> Console
    API --> SDKs
    SDKs --> Starters
    Kernel --> Policy
    Policy --> Deploy

    %% Premium Styling Rules
    style Policy fill:#2d3748,stroke:#4a5568,stroke-width:2px,color:#fff

Source Truth

This page is backed by:

• docs/developer-coverage.manifest.json
• sdk/ts/src/adapters/agent-frameworks.ts
• sdk/ts/src/adapters/agent-frameworks.test.ts
• sdk/ts/README.md
• examples/starters/anthropic/
• examples/starters/google/
• examples/policies/
• docs/architecture/policy-languages.md
• deploy/helm-chart/
• apps/console/
• docs/CONSOLE.md

Supported Public Surfaces

Framework Adapter Helpers

The TypeScript SDK ships compatibility helpers for normalizing tool-call events from common agent frameworks into HELM governance requests. These helpers are source-backed adapter helpers, not full framework runtimes and not vendor certification.

Validation:

make test-sdk-ts

Provider Starters

Example-only means the repository contains a starter layout and smoke script. It does not mean HELM AI Kernel owns the provider SDK or certifies every feature of that ecosystem.

Policy Languages

HELM AI Kernel supports CEL, Rego, and Cedar policy bundle examples.

Use docs/architecture/policy-languages.md for the longer comparison and command examples.

Deployment Surface

The repository keeps Docker, Docker Compose, a Kubernetes Helm chart, and the self-hostable HELM AI Kernel Console. It does not ship hosted operations, a static report viewer, or tenant-admin services in HELM AI Kernel.

Verdict Compatibility

Current HELM AI Kernel runtime docs use ALLOW, DENY, and ESCALATE. Historical docs and generated compatibility code may still contain older verdict labels. Treat them only as migration aliases:

Do not use legacy verdict labels in new runtime docs, policy examples, or quickstart paths.

Source Build Expectations

The retained CI verifies:

• Go build and test for the kernel;
• Python SDK tests;
• TypeScript SDK tests and adapter helper tests;
• Rust SDK build and test;
• Java SDK build and test;
• fixture root verification through the Go verifier;
• docs coverage and docs truth resolution.

make test-all
make docs-coverage
make docs-truth

Unsupported Claim Policy

Do not claim a language, framework, deployment target, or provider integration as supported unless one of these is true:

• docs/developer-coverage.manifest.json has a supported, example-only, or experimental row for it;
• the row points at live source paths and example paths;
• the row names the validation command that proves the claim;
• the public docs page exposes the same claim in Markdown, LLM, and MCP surfaces.

Troubleshooting

MCP 2026 Radar Notes

The original Linear radar item pointed at https://modelcontextprotocol.io/roadmap; as of April 30, 2026 that URL returns a 404 and the current source is MCP Roadmap. The current roadmap frames enterprise-managed auth, gateway/proxy authorization propagation, and finer-grained least-privilege scopes as active enterprise/security directions, while RFC 8707 remains the normative OAuth source for resource indicators. HELM AI Kernel implements this as an additive auth and metadata layer; protocol versions and existing tool schemas remain backward compatible.