---
title: "Verifier Trust Model"
canonical: "https://helm.docs.mindburn.org/security/verifier-trust-model"
source: "helm-ai-enterprise/docs/public/security-and-trust/verifier-trust-model.md"
edit: "https://github.com/Mindburn-Labs/helm-ai-enterprise/edit/main/docs/public/security-and-trust/verifier-trust-model.md"
section: "trust"
access: "public"
sensitivity: "public"
last_reviewed: "2026-04-30"
checksum_sha256: "sha256:0aeb8d00e7eb308dea6799a85167620d3f07cdfb9e3bd2dd0ea979ac5b4b1a94"
build_timestamp: "2026-05-24T13:40:27.882Z"
---
# Offline Verifier Trust Model

## 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: `security/verifier-trust-model`
- Source document: `helm-ai-enterprise/docs/public/security-and-trust/verifier-trust-model.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. |

The HELM Offline Verifier is a standalone tool designed for high-assurance audits and air-gapped verification of EvidencePacks.

## Trust Assumptions
1. **Cryptographic Primitives**: The verifier trusts the mathematical correctness of Ed25519 signatures, SHA-256 hashes, and JCS (RFC 8785) canonicalization.
2. **Standard Compliance**: The verifier assumes the EvidencePack format adheres to the UCS v1.3 specification.
3. **No Network Trust**: The verifier does NOT require network access and does NOT trust results from the HELM server or any proxy.

## Verification Layers
1. **Structural Integrity**: Ensures the bundle contains required indices and manifests.
2. **Content Integrity**: Verifies that every file matches its hash in the signed manifest.
3. **Chain Integrity**: Validates the causal DAG (ProofGraph) and prevents reordering or deletion of events.
4. **Temporal Integrity**: Checks Lamport clock monotonicity across the event stream.
5. **Policy Binding**: Recomputes policy hashes to ensure the Kernel applied the correct rules.

## Auditor Mode
Using the `--json` flag, the verifier produces a machine-readable report containing every check performed, suitable for inclusion in formal compliance artifacts.

## Diagram

```mermaid
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        source["Offline Verifier Trust Model"]
        s0["Trust Assumptions"]
        output["Reader outcome"]
    end

    subgraph Evaluation["2. Evaluation & Policy Plane"]
        s2["Auditor Mode"]
    end

    subgraph Ledger["4. Tamper-Evident Ledger Plane"]
        s1["Verification Layers"]
    end

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

    %% Premium Styling Rules
    style s1 fill:#2f855a,stroke:#276749,stroke-width:2px,color:#fff
    style s2 fill:#2d3748,stroke:#4a5568,stroke-width:2px,color:#fff
```


## Operational Readiness

Use this page as the public operating layer for **Verifier Trust Model**. The source of truth is `helm-ai-enterprise/docs/public/security-and-trust/verifier-trust-model.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.