HELM Source Coverage Map

This page explains how the public HELM docs site maps back to the two HELM source repositories. Use it when you want to know whether a repo surface is published as a full page, summarized by a reference hub, available through the OpenAPI/LLM/MCP exports, or intentionally left as internal implementation material.

Audience

This page is for developers integrating HELM AI Kernel, enterprise evaluators reviewing HELM control-plane and Console material, operators planning a hosted deployment, and reviewers checking whether public docs stay aligned with source.

Outcome

After reading it, you should know where to find the public page for every major HELM surface: install, CLI, SDKs, protocol schemas, examples, conformance, verification, deployment, Console, audit registries, operations, security, and release evidence.

Coverage Model

flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        repo["HELM + HELM AI Kernel repos"]
        manifest["public-docs manifests"]
        pages["Rendered docs pages"]
        llms["llms.txt and llms-full.txt"]
        mcp["Docs MCP tools"]
        source["Edit-source links"]
    end

    subgraph Evaluation["2. Evaluation & Policy Plane"]
        checks["manifest, diagram, coverage, truth checks"]
        release["Validated docs release"]
    end

    %% Operational Flow Edges
    repo --> manifest
    manifest --> pages
    manifest --> llms
    manifest --> mcp
    pages --> source
    pages --> checks
    checks --> release

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

flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        repo["HELM + HELM AI Kernel repos"]
        manifest["public-docs manifests"]
        pages["Rendered docs pages"]
        llms["llms.txt and llms-full.txt"]
        mcp["Docs MCP tools"]
        source["Edit-source links"]
    end

    subgraph Evaluation["2. Evaluation & Policy Plane"]
        checks["manifest, diagram, coverage, truth checks"]
        release["Validated docs release"]
    end

    %% Operational Flow Edges
    repo --> manifest
    manifest --> pages
    manifest --> llms
    manifest --> mcp
    pages --> source
    pages --> checks
    checks --> release

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

The public docs site does not mirror every repo file one-for-one. That would make source-generated ownership READMEs, raw JSON schemas, runbook fragments, and implementation plans harder to use. Instead, the docs publish:

• Full pages for end-to-end developer and evaluator journeys.
• Reference hubs for large source families such as schemas, protocols, examples, deployment, audit registries, and Console.
• Direct OpenAPI export at /openapi.yaml.
• Full Markdown, search, llms-full.txt, and MCP parity for every public page.
• Edit-source links back to the owning repo/path.

HELM AI Kernel Coverage

HELM AI Enterprise Coverage

Publication Rules

HELM publishes public documentation when a source surface is useful to one of the public audiences and does not depend on private credentials, private deployment inventory, unfinished implementation phase notes, or customer-specific runbooks. Internal generated surface READMEs remain source-truth inputs, but the public site normally exposes them through a curated hub page.

Source Truth

The public site is driven by:

• helm-ai-kernel/docs/public-docs.manifest.json
• helm-ai-enterprise/docs/public-docs.manifest.json
• helm-ai-kernel/docs/developer-coverage.manifest.json
• docs-platform/scripts/check-developer-coverage.ts
• docs-platform/scripts/check-diagram-coverage.ts

The HELM AI Kernel repo also runs make docs-coverage docs-truth, which verifies that coverage rows resolve to live source and canonical docs.

Troubleshooting