CompanyArtifactGraph

CompanyArtifactGraph makes work legible.

CompanyArtifactGraph is a source-backed map of company and code work. It helps teams ask questions and find gaps. It does not approve side effects.

Define CompanyArtifactGraph
CompanyArtifactGraph
A source-backed map of company work, like tickets, docs, calls, PRs, and receipts.
Code Intelligence Graph
A read-only map of code files, symbols, routes, calls, tests, and impact.

Artifact examples

Company state is more than docs.

Artifacts are useful because they keep source, permission, stale, disputed, and proof labels close to the work.

Meeting

A source-backed item that can help answer, compare, detect, or prove work.

Decision

A source-backed item that can help answer, compare, detect, or prove work.

Ticket

A source-backed item that can help answer, compare, detect, or prove work.

PR

A source-backed item that can help answer, compare, detect, or prove work.

Commit

A source-backed item that can help answer, compare, detect, or prove work.

Deployment

A source-backed item that can help answer, compare, detect, or prove work.

CustomerInteraction

A source-backed item that can help answer, compare, detect, or prove work.

Spec

A source-backed item that can help answer, compare, detect, or prove work.

KnowledgeClaim

A source-backed item that can help answer, compare, detect, or prove work.

TruthConflict

A source-backed item that can help answer, compare, detect, or prove work.

DriftSignal

A source-backed item that can help answer, compare, detect, or prove work.

ActionProposal

A source-backed item that can help answer, compare, detect, or prove work.

Receipt

A source-backed item that can help answer, compare, detect, or prove work.

EvidencePack

A source-backed item that can help answer, compare, detect, or prove work.

Repo

A source-backed item that can help answer, compare, detect, or prove work.

ChangedFile

A source-backed item that can help answer, compare, detect, or prove work.

CodeSymbol

A source-backed item that can help answer, compare, detect, or prove work.

PublicRoute

A source-backed item that can help answer, compare, detect, or prove work.

TestResult

A source-backed item that can help answer, compare, detect, or prove work.

CodeImpactReport

A source-backed item that can help answer, compare, detect, or prove work.

CodeIndexReceipt

A source-backed item that can help answer, compare, detect, or prove work.

Answer labels

Every query answer carries its evidence state.

Query answer statespermission-aware
LabelMeaning
DraftUseful for proposals, never enough to justify execution.
CanonicalPromoted with provenance, permission state, and receipt references.
DisputedConflicting evidence exists and must be resolved before it can justify work.
StaleFreshness is expired or source reality has moved.

LKS / CKS

Local knowledge and canonical knowledge stay separate.

Useful context can help HELM draft proposals. Only evidence-backed canonical state can support review, and it still cannot bypass the Kernel boundary.

LKS

Local Knowledge State can influence proposals and search. It cannot justify execution.

CKS

Canonical Knowledge State can support execution only with provenance, permission, receipt, and evidence refs.

Boundary

Even canonical company state still hands side effects to HELM AI Kernel for ALLOW, DENY, or ESCALATE.

Lifecycle

Source-backed context can support action, but it cannot approve it.

Artifact lifecycleread path to boundary handoff
StageBoundary
SourceA ticket, decision, PR, deployment, and customer note enter with source and permission labels.
QueryA reviewer asks what changed, which promise it affects, and which source is current.
ConflictHELM marks disputed or stale state as a TruthConflict or DriftSignal instead of treating it as fact.
ProposalThe graph can support a GeneratedSpec, but the draft remains a proposal.
Boundary handoffOnly reviewed action crosses CPI and PEP, then returns receipt-backed proof.

Non-negotiable constraint

The graph is not the authority.

CompanyArtifactGraph can inform proposals, answer safe queries, and surface TruthConflicts or DriftSignals.

All write actions still require review, PEP/CPI execution, and receipt-backed proof.

Define action terms
TruthConflict
A mismatch between what one source says and what another source proves.
DriftSignal
A warning that work is moving away from the plan or policy.
CPI
The check that validates a plan before HELM lets it continue.
PEP
The boundary that enforces the decision before a tool call runs.