HELMhelm-ai-enterprise
MCPLLMs

helm-ai-enterprise

Procurement FAQ

After this page you should know what this surface is for, which source files own the behavior, which public route or adjacent page to use next, and which validation command to run before changing the claim. Public route:
PublicSource-ownedMarkdown export

Audience

Outcome

After this page you should know what this surface is for, which source files own the behavior, which public route or adjacent page to use next, and which validation command to run before changing the claim.

Source Truth

  • Public route: product/procurement
  • Source document: helm-ai-enterprise/docs/public/product/procurement.md
  • Public manifest: helm-ai-enterprise/docs/public-docs.manifest.json
  • Source inventory: helm-ai-enterprise/docs/source-inventory.manifest.json
  • Validation: corepack pnpm run docs:coverage, corepack pnpm run docs:truth, and npm run coverage:inventory from docs-platform

Do not expand this page with unsupported product, SDK, deployment, compliance, or integration claims unless the inventory manifest points to code, schemas, tests, examples, or an owner doc that proves the claim.

Troubleshooting

Symptom First check
A link or route is missing from the docs website Check docs/public-docs.manifest.json, llms.txt, search, and the per-page Markdown export before changing navigation.
A claim is not backed by code or tests Remove the claim or add the missing code, example, schema, or validation command before publishing.

This document provides guidance for organizations evaluating HELM for governing autonomous labor and agentic ecosystems.

Core Value Proposition

HELM separates the Cognitive Plane (stochastic LLMs) from the Truth Plane (deterministic Go kernel). It ensures that no agentic action occurs without mathematical proof and policy compliance.

Key Selection Criteria

  1. Mathematical Determinism: HELM uses JCS (RFC 8785) and Merkle-DAGs to ensure execution is replayable and non-repudiable.
  2. Fail-Closed Governance: The Kernel denies by default. If a policy check fails or a budget is exceeded, the action is blocked.
  3. Pluggable Policy: HELM integrates with industry-standard policy engines like OPA and Cedar.
  4. Offline Verification: EvidencePacks can be verified air-gapped, ensuring total high_assurance control over audit trails.

RFP Compliance

HELM meets or exceeds requirements for:

  • Auditability: Complete causal history via ProofGraph.
  • Traceability: Attribution of every action to a human principal or agent.
  • Containment: Enforced tool sandboxing and drift detection.
  • EU AI Act readiness: High-risk workflow evidence for risk management, event logging, technical documentation, and human oversight on the current 2026-08-02 Annex III application trajectory.
  • US state AI readiness: Colorado SB24-205 and the proposed ADMT replacement are treated as monitored state overlays. HELM records runtime decisions and human-review evidence without depending on a single state deadline as the procurement driver.

Diagram

Diagram1. Ingestion & Context Plane -> Procurement Guide: HELM Autonomous Labor Runtime -> Core Value Proposition -> Key Selection Criteria -> RFP Compliance -> Reader outcome
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        source["Procurement Guide: HELM Autonomous Labor Runtime"]
        s0["Core Value Proposition"]
        s1["Key Selection Criteria"]
        s2["RFP Compliance"]
        output["Reader outcome"]
    end

    %% Operational Flow Edges
    source --> s0
    s0 --> s1
    s1 --> s2
    s2 --> output

    %% Premium Styling Rules
Mermaid source
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        source["Procurement Guide: HELM Autonomous Labor Runtime"]
        s0["Core Value Proposition"]
        s1["Key Selection Criteria"]
        s2["RFP Compliance"]
        output["Reader outcome"]
    end

    %% Operational Flow Edges
    source --> s0
    s0 --> s1
    s1 --> s2
    s2 --> output

    %% Premium Styling Rules

Operational Readiness

Use this page as the public operating layer for Procurement FAQ. The source of truth is helm-ai-enterprise/docs/public/product/procurement.md; if this page and the implementation disagree, update the source-backed doc and rerun the validation command before publishing.

Before relying on this surface, confirm three things: the source path above still exists, the referenced commands or contracts are still present in the owning repo, and the docs-platform export surfaces still show this page in search, Markdown, llms-full.txt, and MCP without exposing protected routes.

Validation command: corepack pnpm run docs:coverage && corepack pnpm run docs:truth. For website parity, also run npm run exports:boundary and npm run thin-pages:check from docs-platform.

Expected Output

A reader should leave with a concrete next action, the source file or contract to inspect, the command that proves the claim, and a clear boundary for what is public versus protected. For reference pages, the expected output is a correctly scoped request, schema, command, or diagnostic path. For operations pages, the expected output is a reproducible readiness or failure signal that can be attached to an evaluation or support thread.

Failure Modes

If the validation command fails, do not patch this page in isolation. First identify whether the drift is in code, generated contracts, source-owner docs, or the docs manifest. If the public page needs a protected deep link, describe the protected document by name instead of exposing its route. Commercial operator details, tenant data, key ceremonies, and deployment-sensitive internals stay in protected customer or staff docs; this public page only exposes the safe developer contract.