Company AI OS Overview

HELM AI Enterprise may be described as the Company AI OS when the full loop is explicit:

1. Query company state from source-backed artifacts.
2. Compare what should be true with what current evidence shows.
3. Generate reviewed work specifications.
4. Govern execution through HELM AI Kernel semantics.
5. Write receipts and evidence back to proof and company-context surfaces.

The public shorthand is:

Models propose. HELM governs execution. Proof records.

This page is explanatory. It does not make HELM AI Enterprise a generally available self-serve product and it does not change the HELM AI Kernel contract.

Public surfaces

• HELM AI Kernel is the public fail-closed execution firewall for AI-agent actions.
• HELM AI Enterprise is the reviewed-access company control-plane direction around the same execution boundary.
• Company context can inform proposals, reconciliation, approvals, and review, but context does not authorize side effects by itself.

Operating loop

Harness State is the operator-facing name for the live context around autonomous work: read/write sets, assumptions, stale dependencies, verification scope, approval state, connector state, sandbox grants, receipt references, and EvidencePack references. It helps operators inspect work before and after execution, but it does not replace HELM's deterministic execution authority.

Diagram

flowchart TD
    subgraph Insight["1. Insight & Context Plane"]
        Docs["Company Source Docs"]
        Tickets["Tickets & Project Boards"]
        PRs["Pull Requests & Release Notes"]
        CAG["CompanyArtifactGraph Ingestion"]
        
        Docs & Tickets & PRs --> CAG
    end

    subgraph Reconciliation["2. Reconciliation Plane"]
        CAG --> State["Live Harness State Context"]
        State --> ShouldIs{"Compare Should vs. Is"}
        ShouldIs -->|Drift Detected| GapAlert["Identify Truth Conflicts & Gaps"]
        ShouldIs -->|Aligned Proposal| SpecGen["Compile GeneratedSpec Draft"]
    end

    subgraph Gate["3. PEP/CPI Enforcement Gate"]
        SpecGen --> CPI["CPI Plan Integrity Verification"]
        CPI --> PEP["PEP Fail-Closed Gate"]
    end

    subgraph Ledger["4. Tamper-Evident Proof Plane"]
        PEP --> Execution["Deterministic Sandbox / Bounded Dispatch"]
        Execution --> JCS["Canonical JCS Payload (RFC 8785)"]
        JCS --> Sign["Cryptographic Signature Ceremony"]
        Sign --> ProofGraph["Append to ProofGraph DAG Ledger"]
        Sign --> Evidence["Assemble EvidencePack Slice Archive"]
    end

    style ShouldIs fill:#2d3748,stroke:#4a5568,stroke-width:2px,color:#fff
    style PEP fill:#e53e3e,stroke:#9b2c2c,stroke-width:2px,color:#fff
    style CPI fill:#3182ce,stroke:#2b6cb0,stroke-width:2px,color:#fff

flowchart TD
    subgraph Insight["1. Insight & Context Plane"]
        Docs["Company Source Docs"]
        Tickets["Tickets & Project Boards"]
        PRs["Pull Requests & Release Notes"]
        CAG["CompanyArtifactGraph Ingestion"]
        
        Docs & Tickets & PRs --> CAG
    end

    subgraph Reconciliation["2. Reconciliation Plane"]
        CAG --> State["Live Harness State Context"]
        State --> ShouldIs{"Compare Should vs. Is"}
        ShouldIs -->|Drift Detected| GapAlert["Identify Truth Conflicts & Gaps"]
        ShouldIs -->|Aligned Proposal| SpecGen["Compile GeneratedSpec Draft"]
    end

    subgraph Gate["3. PEP/CPI Enforcement Gate"]
        SpecGen --> CPI["CPI Plan Integrity Verification"]
        CPI --> PEP["PEP Fail-Closed Gate"]
    end

    subgraph Ledger["4. Tamper-Evident Proof Plane"]
        PEP --> Execution["Deterministic Sandbox / Bounded Dispatch"]
        Execution --> JCS["Canonical JCS Payload (RFC 8785)"]
        JCS --> Sign["Cryptographic Signature Ceremony"]
        Sign --> ProofGraph["Append to ProofGraph DAG Ledger"]
        Sign --> Evidence["Assemble EvidencePack Slice Archive"]
    end

    style ShouldIs fill:#2d3748,stroke:#4a5568,stroke-width:2px,color:#fff
    style PEP fill:#e53e3e,stroke:#9b2c2c,stroke-width:2px,color:#fff
    style CPI fill:#3182ce,stroke:#2b6cb0,stroke-width:2px,color:#fff

Source posture

These docs use the public Mindburn and HELM claim posture:

• HELM AI Kernel remains the public Kernel surface.
• HELM AI Enterprise remains reviewed-access product direction.
• CompanyArtifactGraph is query and reconciliation memory, not authority.
• OrgGenome Compiler output is draft until reviewed and promoted.
• Harness State is inspectable company execution context, not a side-effect gate.
• ALLOW, DENY, and ESCALATE are the public verdict terms.

Source truth

• Kernel boundary, verdicts, receipts, ProofGraph, EvidencePack, replay, and conformance: helm-ai-kernel/README.md, helm-ai-kernel/api/openapi/, helm-ai-kernel/sdk/ts/src/client.ts, helm-ai-kernel/protocols/conformance/v1/test-vectors.json, helm-ai-kernel/tests/conformance/, and helm-ai-kernel/reference_packs/.
• Enterprise Company AI OS framing, CompanyArtifactGraph, GeneratedSpec loop, connector governance, proof routes, and reviewed-access posture: helm-ai-enterprise/README.md, helm-ai-enterprise/api/openapi/helm.openapi.yaml, helm-ai-enterprise/apps/console/src/router/routes.tsx, helm-ai-enterprise/packages/helm-ai-enterprise-design-system/src/routes/blueprints.ts, and helm-ai-enterprise/commercial/.
• OrgGenome Compiler draft material, dataset/schema registry, training, evaluation, and serving boundaries: orggenome-compiler/README.md, orggenome-compiler/datasets/README.md, orggenome-compiler/datasets/schemas/, and orggenome-compiler/docs/.

Where to go next

• Authority boundary
• CompanyArtifactGraph
• OrgGenome Compiler
• Proof and replay
• Workstation governance
• Connector drift