---
title: "HELM Source Coverage Map"
canonical: "https://helm.docs.mindburn.org/coverage"
source: "helm-ai-enterprise/docs/public/source-coverage.md"
edit: "https://github.com/Mindburn-Labs/helm-ai-enterprise/edit/main/docs/public/source-coverage.md"
section: "coverage"
access: "public"
sensitivity: "public"
last_reviewed: "2026-05-05"
checksum_sha256: "sha256:6bce084fb38c1bab0b16bd3bfcdcb1da32d7b13db1c49c584c6eabbf1e60dbdb"
build_timestamp: "2026-05-24T13:40:27.882Z"
---
# 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

```mermaid
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

| Source family | Repo evidence | Public docs route |
| --- | --- | --- |
| Kernel, CLI, receipts, policy boundary | `helm-ai-kernel/core/`, `helm-ai-kernel/docs/ARCHITECTURE.md`, `helm-ai-kernel/docs/DEVELOPER_JOURNEY.md` | `/helm-ai-kernel`, `/helm-ai-kernel/developer-journey`, `/helm-ai-kernel/architecture` |
| Install and local proxy path | `helm-ai-kernel/docs/QUICKSTART.md`, `helm-ai-kernel/Makefile`, `helm-ai-kernel/.goreleaser.yml` | `/helm-ai-kernel/quickstart`, `/helm-ai-kernel/developer-journey` |
| Deployment and examples | `helm-ai-kernel/deploy/`, `helm-ai-kernel/docker-compose.yml`, `helm-ai-kernel/examples/` | `/helm-ai-kernel/deployment-and-examples` |
| SDKs and language clients | `helm-ai-kernel/sdk/`, `helm-ai-kernel/examples/*_client/`, `helm-ai-kernel/docs/sdks/00_INDEX.md` | `/helm-ai-kernel/sdks` |
| OpenAI-compatible proxy and MCP | `helm-ai-kernel/docs/INTEGRATIONS/`, `helm-ai-kernel/examples/*openai_baseurl/`, `helm-ai-kernel/examples/mcp_client/` | `/helm-ai-kernel/integrations/openai-compatible-proxy`, `/helm-ai-kernel/integrations/mcp` |
| Protocols, schemas, policy language, conformance | `helm-ai-kernel/protocols/`, `helm-ai-kernel/schemas/`, `helm-ai-kernel/docs/architecture/policy-languages.md` | `/helm-ai-kernel/reference/protocols-and-schemas`, `/helm-ai-kernel/conformance`, `/helm-ai-kernel/compatibility` |
| Verification and evidence packs | `helm-ai-kernel/docs/VERIFICATION.md`, `helm-ai-kernel/protocols/spec/evidence-pack-v1.md`, `helm-ai-kernel/examples/receipt_verification/` | `/helm-ai-kernel/verification`, `/helm-ai-kernel/developer-journey` |
| Release, security, supply chain | `helm-ai-kernel/SECURITY.md`, `helm-ai-kernel/RELEASE.md`, `helm-ai-kernel/BEST_PRACTICES.md`, `helm-ai-kernel/release/` | `/helm-ai-kernel/security/release-security`, `/helm-ai-kernel/publishing` |

## HELM AI Enterprise Coverage

| Source family | Repo evidence | Public docs route |
| --- | --- | --- |
| Five-minute integration | `helm-ai-enterprise/docs/public/getting-started/integrate-in-5-min.md` | `/start` |
| Individual governance | `helm-ai-enterprise/docs/public/product/agent-skills-governance.md`, policy bundle docs | `/helm-ai-enterprise/individual`, `/product/policy-bundles` |
| Enterprise control plane | `helm-ai-enterprise/docs/COMMERCIAL_OVERVIEW.md`, `helm-ai-enterprise/docs/COMMERCIAL_DEPLOY.md` | `/enterprise` |
| Console | `helm-ai-enterprise/docs/console/` | `/product/console` |
| Observability and tracing | `helm-ai-enterprise/docs/public/observability/observability.md`, `helm-ai-enterprise/docs/public/tracing.md` | `/observability`, `/tracing` |
| API and audit registries | `helm-ai-enterprise/docs/api/`, `helm-ai-enterprise/docs/audit/`, `helm-ai-enterprise/api/openapi/` | `/reference`, `/reference/api-and-audit-registries`, `/openapi.yaml` |
| Operations | `helm-ai-enterprise/docs/operations/` | `/operations/operator-guide` |
| Security, TCB, threat model, verifier trust | `helm-ai-enterprise/docs/public/security-and-trust/` | `/proof`, `/security/threat-model`, `/security/tcb-policy`, `/security/verifier-trust-model` |
| Procurement, regional, and RFP material | `helm-ai-enterprise/docs/public/product/` | `/product/procurement`, `/product/regional-compat`, `/product/rfp-answers` |

## 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

| Symptom | Check |
| --- | --- |
| A repo doc is not visible on the site | Look for the source family in this page, then check the manifest for its public hub or direct page. |
| A public page links to stale source | Run `npm run validate` in `docs-platform` and `make docs-coverage docs-truth` in `helm-ai-kernel`. |
| A claim appears in docs without source evidence | Add or correct the row in `developer-coverage.manifest.json`, then rerun `npm run coverage:check`. |
| A page is missing from agent exports | Check `/llms.txt`, `/llms-full.txt`, `/mcp`, and the search index generated by the docs platform. |