HELMReference
MCPLLMs

Reference

Specs, Research, and Source Families

OpenAPI, schemas, protocols, CLI, SDKs, generated examples, and error codes.
PublicSource-ownedMarkdown export
HELM Decision PathEvery governed call produces receipts that can be inspected, exported, and verified.
HELM Decision PathAI ClientOpenAI-compatible SDKHELM Proxybase URL boundaryPolicy Engineallow / deny / requireReceiptsigned decision recordVerifieroffline evidence checks

This page closes the public coverage gap between the HELM docs site and the large internal source families in the HELM repo. It does not publish every internal note as a standalone public page; it documents the owner route for each active family and points to the public surface that carries the source truth.

Audience

Use this page if you are auditing source coverage, building against advanced HELM internals, reviewing specs/research material, or trying to find the public route for a repo family that is not a top-level navigation item.

Outcome

You should know how apps, core, modules, packs, protocols, schemas, infra, scripts, services, docs/specs, docs/research, and UI/design system material map into public docs, LLM exports, MCP, and validation gates.

Coverage Topology

Diagram1. Ingestion & Context Plane -> Source-family rules -> Direct public pages -> Public hub pages -> Internal/source-only classifications -> Markdown / LLM / MCP -> 4. Tamper-Evident Ledger Plane -> documentation-coverage.csv
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        families["Source-family rules"]
        direct["Direct public pages"]
        hubs["Public hub pages"]
        internal["Internal/source-only classifications"]
        exports["Markdown / LLM / MCP"]
    end

    subgraph Ledger["4. Tamper-Evident Ledger Plane"]
        ledger["documentation-coverage.csv"]
        audit["Audit ledger with rationale"]
    end

    %% Operational Flow Edges
    ledger --> families
    families --> direct
    families --> hubs
    families --> internal
    direct --> exports
    hubs --> exports
    internal --> audit

    %% Premium Styling Rules
    style ledger fill:#2f855a,stroke:#276749,stroke-width:2px,color:#fff
    style audit fill:#2f855a,stroke:#276749,stroke-width:2px,color:#fff
Mermaid source
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        families["Source-family rules"]
        direct["Direct public pages"]
        hubs["Public hub pages"]
        internal["Internal/source-only classifications"]
        exports["Markdown / LLM / MCP"]
    end

    subgraph Ledger["4. Tamper-Evident Ledger Plane"]
        ledger["documentation-coverage.csv"]
        audit["Audit ledger with rationale"]
    end

    %% Operational Flow Edges
    ledger --> families
    families --> direct
    families --> hubs
    families --> internal
    direct --> exports
    hubs --> exports
    internal --> audit

    %% Premium Styling Rules
    style ledger fill:#2f855a,stroke:#276749,stroke-width:2px,color:#fff
    style audit fill:#2f855a,stroke:#276749,stroke-width:2px,color:#fff

HELM Source Families

Source family Active rows Public route or classification
apps/ 43 /enterprise, /product/console, /operations/operator-guide
core/ 132 /reference, /proof, /reference/verify, /operations/operator-guide
examples/ 19 /integrations/openai-baseurl, /integrations/vercel-ai-sdk, /integrations/langchain, /integrations/mcp, /reference/sdks
modules/ 23 /product/console and this page
packs/ 16 /product/policy-bundles, /reference, /product/eu-ai-act-high-risk
protocols/ 160 /helm-ai-kernel/reference/protocols-and-schemas, /reference
schemas/ 28 /helm-ai-kernel/reference/protocols-and-schemas, /reference/api-and-audit-registries
sdk/ 16 /reference/sdks, /helm-ai-kernel/sdks
packages/ 25 /product/design-system, /reference/sdks, /reference/cli-v3/format
infra/, deploy/, ops/ 21 /operations/operator-guide
scripts/, tools/, qa/, tests/, e2e/ 40 /coverage, /operations/operator-guide, and source-only validation ledgers
services/ 3 /integrations/mcp, /product/console, high-risk-loop bridge source docs
docs/specs/, docs/research/ Source-led docs This page, /reference, /proof, /enterprise
docs/ui/, design-system package docs Source-led docs /product/design-system, /product/console

Public versus Source-Only

Some source rows are intentionally not standalone public pages:

  • generated ownership READMEs
  • migration files where the public contract is the deployment or schema guide
  • CI workflow implementation details where the public contract is release, supply-chain, or validation behavior
  • test fixtures where the public contract is conformance, verification, or example behavior
  • private deployment inventory values and customer-specific runbooks

Those rows still need a coverage rule. The source-coverage gate fails when a row does not match a public route or an explicit classification.

Source Truth

  • helm-ai-enterprise/docs/documentation-coverage.csv
  • helm-ai-enterprise/scripts/check_documentation_coverage.py
  • helm-ai-enterprise/scripts/check_documentation_truth.py
  • helm-ai-enterprise/docs/public-docs.manifest.json
  • helm-ai-kernel/docs/public-docs.manifest.json
  • docs-platform/scripts/check-helm-source-coverage.ts

Troubleshooting

Symptom Check
A source path is not findable from public docs Run npm run helm-source:check and inspect the unmatched row.
A hub page claims a family that no longer exists The source-coverage gate checks repo paths and will fail.
A public docs page misses a diagram npm run diagrams:check fails with the exact slug and source path.
A source-only classification feels too broad Split the family into a direct public page and update the rule.