---
title: "CompanyArtifactGraph"
canonical: "https://helm.docs.mindburn.org/company-ai-os/company-artifact-graph"
source: "docs-platform/content/docs/company-ai-os/company-artifact-graph.md"
edit: "https://github.com/Mindburn-Labs/docs-platform/edit/main/content/docs/company-ai-os/company-artifact-graph.md"
section: "company-ai-os"
access: "public"
sensitivity: "public"
last_reviewed: "2026-05-17"
checksum_sha256: "sha256:baaa7f697f7613c18558a5b6da855b2f5ef52e13351f0f23331b490e1f9873af"
build_timestamp: "2026-05-24T13:40:27.882Z"
---
# CompanyArtifactGraph

CompanyArtifactGraph is the explanatory name for source-backed company memory in the HELM AI Enterprise direction.

It can organize artifacts such as:

- policies and operating rules
- tickets and project records
- pull requests and release notes
- customer commitments and support records
- approvals, receipts, and proof references
- incident records and follow-up work

## What it is for

CompanyArtifactGraph helps the company become queryable and reconcilable. It lets an operator ask what changed, which source supports a claim, where a promise conflicts with shipped behavior, and which proof record belongs to a decision.

It also contributes to Harness State: the operator-facing view of transactional autonomous-work context, including read sets, write sets, assumptions, stale dependencies, verification scope, approvals, and proof references. Harness State is a review and reconciliation surface. It is not execution authority.

## What it is not for

CompanyArtifactGraph is not the side-effect gate.

A graph result can inform a proposal or review path, but real execution still needs HELM checks. Treating graph memory as authority would collapse the separation between knowledge and action.

## Safe public wording

Use wording like:

- "CompanyArtifactGraph organizes source-backed context."
- "CompanyArtifactGraph helps identify drift and truth conflicts."
- "CompanyArtifactGraph can point to receipts and evidence."

Avoid wording like:

- "CompanyArtifactGraph authorizes actions."
- "The graph decides what to execute."
- "Memory makes the company autonomous."

## Relationship to proof

Receipts, ProofGraph records, and EvidencePacks can be referenced from company-context surfaces. That does not mean raw company data should be published or treated as proof by itself.

The safe distinction is:

- Context explains why a proposal exists.
- HELM evaluates whether it may run.
- Proof records what happened.

Harness State follows the same boundary:

- CompanyArtifactGraph can show `reads_from`, `writes_to`, `assumes`, `invalidates`, `blocked_by_policy`, and `proven_by_receipt` edges.
- GeneratedSpecs can carry read/write sets, assumptions, stale dependency references, rollback policy, human review state, and verification scope.
- PEP/CPI still decide whether side effects may dispatch.

## Diagram

```mermaid
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Ingestion"]
        Policies["Company Policies & Standard Operating Procedures"]
        Tickets["Jira / GitHub Issues & Task Records"]
        PRs["Pull Requests, Diff Logs, and Release Notes"]
        Commitments["Customer Promises & Support Agreements"]
        
        Policies & Tickets & PRs & Commitments --> CAG["CompanyArtifactGraph Compiler"]
    end

    subgraph Memory["2. Semantic Graph Plane"]
        CAG --> GraphDb["Active Artifact Relationship Graph"]
        
        subgraph Edges["Semantic Relationship Mappings"]
            direction LR
            E1["reads_from"]
            E2["writes_to"]
            E3["assumes"]
            E4["invalidates"]
            E5["blocked_by_policy"]
            E6["proven_by_receipt"]
        end
        GraphDb --> Edges
    end

    subgraph Context["3. Harness State Operational Context"]
        Edges --> Harness["Harness State Context Manager"]
        
        Harness --> ReadSet["Read Sets & Stale Dependency Checks"]
        Harness --> WriteSet["Write Sets & Mutation Boundaries"]
        Harness --> Assumptions["Active Reasoning Assumptions"]
        
        ReadSet & WriteSet & Assumptions --> Spec["GeneratedSpec (Reviewed Action Plan)"]
    end

    subgraph Gate["4. Deterministic Enforcement Gate"]
        Spec --> CPI["CPI Plan Integrity Verification"]
        CPI --> PEP{"HELM PEP Decision Engine"}
        
        PEP -->|ALLOW| Exec["Execution & Proof receipt committed"]
        PEP -->|DENY / ESCALATE| Block["Execution blocked or paused"]
    end

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

## Source truth

- Enterprise Company AI OS and CompanyArtifactGraph framing: `helm-ai-enterprise/README.md`.
- Enterprise API source family for Company Artifact Graph, should-vs-is detection, GeneratedSpec, ProofGraph, EvidencePack, and connector governance: `helm-ai-enterprise/api/openapi/helm.openapi.yaml`.
- Enterprise Console route and product-surface evidence for proof, receipts, connectors, and replay: `helm-ai-enterprise/apps/console/src/router/routes.tsx` and `helm-ai-enterprise/packages/helm-ai-enterprise-design-system/src/routes/blueprints.ts`.
- Kernel proof and receipt boundary that remains authoritative for execution: `helm-ai-kernel/README.md`, `helm-ai-kernel/api/openapi/`, and `helm-ai-kernel/sdk/ts/src/client.ts`.