verify = is it valid?replay = can it be reproduced?diff = what changed?The Verifier Trilogy. Three commands. Three questions. Every attestation answered from the command line. A single 3.1 MB binary with SHA3-256 verification, zero runtime dependencies, and deterministic output. No API key required.
h33-cli v0.2.0 — Rust — MIT License
Three methods. All produce the same h33 binary. All produce identical verification results.
cargo install h33-cli
brew tap H33ai-postquantum/hics
brew install h33
# macOS (Apple Silicon)
curl -fsSL https://github.com/H33ai-postquantum/h33-cli-rs/releases/latest/download/h33-aarch64-apple-darwin -o h33
chmod +x h33 && sudo mv h33 /usr/local/bin/
Verification commands require no configuration. No API key, no config file, no network access. Install and verify immediately.
From install to verified receipt in under sixty seconds.
# 1. Verify a receipt
$ h33 verify receipt receipt.json
# 2. Diff two receipts — see what changed and why it matters
$ h33 diff receipt before.json after.json
# 3. Replay a session for determinism
$ h33 replay session session.json
# 4. Inspect the receipt schema
$ h33 inspect schema
Four subcommands for receipt, session, proof, and directory verification. Each produces a deterministic PASS/FAIL verdict with structured field-level output.
Verify a receipt JSON file. Checks field formats, hash integrity, signature status, H33-74 commitment, and chain linkage.
Alias: h33 verify r
Verifying receipt.json
PASS receipt_id f47ac10b-58cc-4372-a567-0e02b2c3d479
PASS node_hash_format c3d4e5f6...a1b2c3d4
PASS previous_hash_format genesis
PASS dag_root_format d4e5f6a1...b2c3d4e5
PASS agent_identity a1b2c3d4...e5f6a1b2
PASS session_binding sess-001
PASS canonical_name h33.agent.acme.finance.auditor.prod.001
PASS signature_status signed
PASS h33_74_status committed
PASS verification_url https://api.h33.ai/...
PASS timestamp 2026-05-23T14:30:00Z
VERDICT VALID
Verify an entire session chain — an ordered array of receipts. Validates each receipt individually, then verifies cross-receipt chain integrity (previous_hash linkage).
Alias: h33 verify s
Verify a receipt against the public proof endpoint. No API key required. Fetches the receipt by ID from the H33 public API and validates it independently.
Alias: h33 verify p
# Fetches receipt from public endpoint, verifies locally
# No API key. No account. Anyone can verify.
PASS receipt_id f47ac10b-58cc-4372-a567-0e02b2c3d479
PASS public_proof verified against api.h33.ai
VERDICT VALID
Verify every receipt JSON file in a directory. Reports individual and aggregate results. Suitable for batch auditing and CI pipelines.
Alias: h33 verify d
Verifying 47 receipts in ./receipts/
PASS receipt-001.json
PASS receipt-002.json
PASS receipt-003.json
...
PASS receipt-047.json
47 verified, 0 failed
VERDICT VALID
| Flag | Effect |
|---|---|
--online |
Cross-check the receipt against the H33 public API. No API key required. |
--strict |
Treat warnings as failures. Any non-PASS check produces exit code 1. |
--chain |
Verify chain continuity — confirm previous_hash linkage across receipts. |
--json |
Output machine-readable JSON instead of human-readable terminal format. |
Semantic diffing that understands receipt structure. Changes are categorized by operational impact: identity, execution path, governance state, policy output, attestation, and temporal drift.
Field-level semantic comparison of two receipt files. Changes sorted by severity (critical first) and grouped by category.
Alias: h33 diff r | Exit code 1 if critical changes detected
Diff: before.json ↔ after.json
IDENTITY
info id receipt_id f47ac10b… → a1234567…
EXECUTION PATH
CRIT exec dag_root d4e5f6a1b2c3…d4e5 → f6a1b2c3d4e5…f6a1
CRIT exec node_hash c3d4e5f6a1b2…c3d4 → e5f6a1b2c3d4…e5f6
CRIT exec previous_hash 000000000000…0000 → c3d4e5f6a1b2…c3d4
GOVERNANCE STATE
warn gov h33_74_status pending → committed
warn gov signature_status signed → verified
POLICY OUTPUT
warn policy policy_decision allow → deny
warn policy exposure_status not_exposed → encrypted_only
warn policy approval_status + pending_quorum
TOTAL 3 critical, 5 warnings, 4 info
VERDICT DIVERGEDStructural and semantic comparison of two session chains. Shows divergence point, per-receipt diffs, and frame hash comparison.
Alias: h33 diff s
Session Diff
Left
File original.json
Receipts 2
Frame hash 602b7c58…
Right
File modified.json
Receipts 2
Frame hash b74ddcf7…
DIVERGED Divergence at receipt index 1
─ Receipt [1]
CRIT exec node_hash bbbbbbbbbbbb…bbbb → cccccccccccc…cccc
CRIT exec dag_root eeeeeeeeeeee…eeee → ffffffffffff…
warn gov signature_status signed → verified
warn gov h33_74_status committed → anchored
Change Summary
2 critical, 2 warningsBatch comparison of two receipt directories. Shows files only in one side, modified files with category breakdowns, and identical files count.
Alias: h33 diff d
| Category | Fields | Significance |
|---|---|---|
| IDENTITY | agent_id, canonical_name, session_id | Who is acting |
| EXECUTION PATH | node_hash, previous_hash, dag_root | What was computed (always CRITICAL) |
| GOVERNANCE STATE | signature_status, h33_74_status | How it was attested |
| POLICY OUTPUT | policy_decision, exposure_status, approval_status | What was decided |
| ATTESTATION | verification_url, replay_ref | Where to verify |
| TEMPORAL | timestamp | When it happened |
Replay sessions to verify determinism. Compare forked sessions to find divergence. Compute frame hashes at arbitrary timestamps. Replay is the core primitive for independent verification.
Replay a session file and verify deterministic reproducibility. Recomputes the frame hash from receipt data and compares against the declared value. Runs multiple iterations to confirm consistency.
Alias: h33 replay s | Default iterations: 10
Replay: session.json
Receipts 3
Session sess-001
Agent a1b2c3d4...
frame_hash 444ba675074d9dc6...
determinism DETERMINISTIC (100 iterations, 0ms)
time_range 2026-05-23T14:30:00Z → 2026-05-23T14:30:02Z
PASS chain integrity verified
VERDICT REPLAY VERIFIED
Compare two session files and identify the exact point of divergence. Shows which receipt index, timestamp, and field values differ. Critical for incident investigation and audit trail analysis.
Alias: h33 replay f
Comparing sessions...
Original sess-001 (5 receipts)
Forked sess-001-fork (5 receipts)
Shared prefix 3 receipts
DIVERGENCE at index 3
timestamp 2026-05-23T14:30:03Z
original hash aabb1122...
forked hash ccdd3344...
Compute the canonical frame hash for a session or receipt file. Optionally compute at a specific timestamp for point-in-time verification.
Alias: h33 replay h
444ba675074d9dc6a8e2f1b3c5d7e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6
Human-readable visualization of receipts, sessions, and schema definitions. Designed for auditors who need to read the data, not just validate it.
Pretty-print a receipt with field annotations. Truncates long hashes for readability while preserving enough characters for identification. Shows schema-level annotations for each field.
Alias: h33 inspect r
Visualize the session as a directed acyclic graph. Shows chain linkage with terminal-style connectors, signature status, and H33-74 commitment state for each node.
Alias: h33 inspect s
Session DAG — 3 nodes
Session sess-001
Agent a1b2c3d4...
Session root 8a12947c834b4b25...
┌ [0] aaaaaaaaaaaa… r-001
│ prev: genesis sig: signed h33-74: committed
│
├ [1] bbbbbbbbbbbb… r-002
│ prev: aaaaaaaaaaaa… sig: signed h33-74: committed
│
├ [2] cccccccccccc… r-003
└ prev: bbbbbbbbbbbb… sig: verified h33-74: anchored
PASS chain integrity verified across 2 links
Display the receipt field definitions, types, and constraints. Useful as a reference when building integrations or reviewing receipt structures.
Full governance interaction from the command line. Query status, visualize graphs, verify state, replay decisions, detect drift, and run the governance copilot.
Query the current governance state. Returns active sessions, pending attestations, and system health.
Visualize the governance graph structure. Shows nodes, edges, and attestation coverage.
Verify the integrity of the governance state. Checks all chain linkages and attestation validity.
Replay governance decisions from the chain. Reconstruct the decision history at any point in time.
Detect drift between declared governance state and actual system behavior. Surfaces discrepancies.
Interactive governance assistant. Walks through verification steps with guided prompts and explanations.
Purpose-built workflows for auditors, enterprises, regulators, SDK developers, and AI orchestration pipelines.
Verify the full receipt chain, inspect the session DAG for anomalies, then export structured JSON for your audit workpapers.
# 1. Verify chain integrity
h33 verify session session.json --chain --strict
# 2. Inspect the DAG visually
h33 inspect session session.json
# 3. Export for workpapers
h33 verify session session.json --json > audit.json
Verify all receipts in a directory as part of your deployment pipeline. Strict mode ensures no warnings pass through to production.
# Batch verify all receipts
h33 verify dir ./receipts/ --strict
# Cross-check against public API
h33 verify dir ./receipts/ --online --strict
Look up any receipt by ID without an API key. Replay sessions at specific timestamps to reconstruct the state at any point in time.
# Public lookup (no API key)
h33 verify proof f47ac10b-58cc...
# Replay at a specific moment
h33 replay session session.json \
--at 2026-05-23T14:30:00Z
Use --json for machine-readable output in your test suites. Verify your SDK produces receipts that pass the same checks.
# Machine-readable output
h33 verify receipt receipt.json --json
# Validate SDK-generated receipts
h33 verify dir ./test-output/ --strict --json
Integrate into agent workflows. Pipe JSON output to jq for field extraction. Use exit codes to gate downstream actions.
# Extract verdict programmatically
h33 verify receipt r.json --json | jq '.verdict'
# Gate on exit code
h33 verify session s.json --strict \
&& echo "Proceeding" \
|| echo "Halting pipeline"
Add receipt verification to your deployment pipeline. Fails the build if any receipt is invalid or any chain link is broken.
name: Verify Governance Receipts
on: [push, pull_request]
jobs:
verify:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install H33 CLI
run: cargo install h33-cli
- name: Verify all receipts
run: h33 verify dir ./governance/receipts/ --strict --json
- name: Replay session determinism
run: h33 replay session ./governance/session.json --iterations 100
- name: Verify chain integrity
run: h33 verify session ./governance/session.json --chain --strict
Exit code 0 = all checks pass, build succeeds. Exit code 1 = at least one check failed, build fails. No ambiguity.
Optional configuration for API access and governance commands. Verification commands operate without any configuration.
# API base URL (default: https://api.h33.ai)
api_base = "https://api.h33.ai"
# API key (only for governance commands)
api_key = "h33_sk_..."
| Variable | Purpose |
|---|---|
H33_API_BASE |
Override the API base URL |
H33_API_KEY |
API key for governance commands |
Environment variables override config file values. Verification commands (verify, replay, inspect) require no configuration at all.
Three exit codes. Unambiguous. Machine-parseable. Designed for CI pipelines and automated workflows.
--online), or configuration error.Every command, flag, and alias in one table.
| Command | Description | Flags | Alias |
|---|---|---|---|
h33 verify receipt <path> |
Verify a receipt JSON file | --online --strict --chain --json |
h33 verify r |
h33 verify session <path> |
Verify session chain (array of receipts) | --online --strict --chain --json |
h33 verify s |
h33 verify proof <id> |
Verify receipt via public proof endpoint | — | h33 verify p |
h33 verify dir <path> |
Verify all receipts in a directory | --online --strict --json |
h33 verify d |
h33 replay session <path> |
Replay session, verify determinism | --at --iterations --json |
h33 replay s |
h33 replay fork <a> <b> |
Compare two sessions, find divergence | — | h33 replay f |
h33 replay hash <path> |
Compute canonical frame hash | --at |
h33 replay h |
h33 inspect receipt <path> |
Pretty-print with field annotations | — | h33 inspect r |
h33 inspect session <path> |
Visualize session DAG | — | h33 inspect s |
h33 inspect schema |
Show receipt field definitions | — | — |
h33 governance <sub> |
status | graph | verify | replay | drift | copilot | — | — |
The h33-cli trilogy (above) is the general-purpose H33-74 receipt verifier. Beyond it, six substrate-specific verifiers cover the L5 FHE stack, ZK-256, PQ-signed releases, Trustless Decision Attestations, regulatory submissions, and lattice-estimator artifacts. Every artifact H33 produces verifies offline with one of these tools. None call H33.
$h33-fhe-verify verify <bundle.bin>
$h33-zk-256-verify verify <bundle.bin>
$h33-verify-release verify <manifest.json>
$h33-verify-attestation verify <receipt.bin>
$h33-verify-submission verify <bundle.bin>
$python3 verify_manifest.py <artifact.json>
If H33 makes a claim and a buyer can’t verify it offline, that’s a gap in the substrate — not a feature of the relationship.
“The artifact is the trust unit. H33’s continued existence is not a precondition for verifiability.”
Source code, releases, and issue tracker for h33-cli.
Canonical test vectors for independent verifier implementations.
Adversarial validation suite. 54 tests. Deterministic replay verification.
Full specification for agent attestation, sessions, and receipt schemas.
TypeScript SDK for agent attestation. Generates the receipts this CLI verifies.
Model Context Protocol SDK. MCP server attestation and verification.
Browser-based receipt verification. Same checks as the CLI.
REST API documentation for the H33 attestation and verification endpoints.
Install the CLI. Verify your first receipt. Integrate into your pipeline. Independent verification in under sixty seconds.