一致性级别

Conformance levels let you prove — to auditors, regulators, or your own team — that HELM is enforcing specific guarantees. Each level builds on the previous one.

HELM ships L1 + L2 + L3. L3 is shipped, but not yet adversarially tested.

---

At a glance

Level	Name	Gates	Status
L1	Core Kernel	6	✅ Shipped
L2	Operational	12 (includes L1)	✅ Shipped
L3	Enterprise	15 (includes L2)	✅ Shipped

---

L1 — Core Kernel Correctness

6 gates covering the structural foundations of governed execution.

Gate	What it ensures
JCS Canonicalization	RFC 8785 deterministic JSON serialization
PEP Boundary	Schema validation on both input and output
Ed25519 Signatures	Every receipt is cryptographically signed
Lamport Clock	Monotonic causal ordering across all receipts
ProofGraph DAG	Append-only, hash-chained receipt graph
Trust Registry	Event-sourced key lifecycle management

What you can tell auditors: "Every decision has non-repudiable proof with deterministic ordering."

---

L2 — Operational Correctness

12 gates — all of L1 plus enforcement and verification capabilities.

Gate	What it ensures
WASI Sandbox	Gas, time, and memory bounds enforced
Approval Ceremony	Timelock + 4-hash challenge/response with Ed25519
Evidence Pack	Deterministic export (same content → same SHA-256)
Offline Replay	Replay from genesis without network
Output Drift	SHA-256 output hash mismatch detection
Idempotency	Receipt-based duplicate rejection

What you can tell auditors: "Execution history is tamper-evident, compute is bounded, and everything is offline-verifiable."

---

L3 — Enterprise Correctness (Shipped)

3 additional gates. Shipped in the product, but not yet adversarially tested.

Gate	What it ensures
G13 — HSM Key Management	Hardware-backed signing with ceremony-based rotation
G14 — Policy Bundle Integrity	Signed bundles with content-addressed loading
G15 — Proof Condensation	Merkle checkpoints for long-running sessions

What you can tell auditors: "Hardware root of trust, tamper-proof policy distribution, and efficient long-term storage."

---

Run conformance

# Build the kernel
make build

# Run L1
./bin/helm conform --level L1 --json

# Run L2 (includes all L1 gates)
./bin/helm conform --level L2 --json

Expected output (L2)

{
  "profile": "L2",
  "verdict": "PASS",
  "gates": 12,
  "failed": 0,
  "details": {
    "jcs_canonicalization": "PASS",
    "pep_boundary": "PASS",
    "wasi_sandbox": "PASS",
    "approval_ceremony": "PASS",
    "proofgraph_dag": "PASS",
    "trust_registry": "PASS",
    "evidence_pack": "PASS",
    "offline_replay": "PASS",
    "output_drift": "PASS",
    "idempotency": "PASS",
    "island_mode": "PASS",
    "conformance_gates": "PASS"
  }
}

Run all 12 use cases

make crucible

Runs UC-001 through UC-012, testing every enforcement property end-to-end.

---

CI integration

Conformance runs inside the main CI workflow on every push to main. See .github/workflows/ci.yml for the build, test, and docs verification gates.

---

Next steps

Goal	Guide
Get running in 5 minutes	Quickstart
Understand the trust model	Trust Model
Verify a release offline	Verify & Export