Agent-008 — Agent GovernanceHATS — Cyber InsuranceH33-74 — Portable ProofPQ Verified — PQ ValidationCryptographic APIs
AIR
The Cryptographic Lifecycle
How It WorksWatch DemoThe MapPatent Portfolio
Architecture
H33-RootAgent-ZeroQ-SignReplayTruth
Cryptographic Services
UpstreamFHE-IQBFVCKKSTFHE
Open Standards
HATSHICSPQ-Verified (New)CRVOISQ-Key
Verification
Conformance SuiteVerification GuaranteesHATS SpecificationArchitectureProtocol Stability
Proof Lab
Cyber Insurance (HATS)BankingGovernmentHealthcareLaw FirmsPayments (WireProof)AI Companies
SDKs & Tools
SDKs HubTypeScript SDKMCP SDKVerifier CLIGitHub
References
DocumentationAPI ReferenceConformance VectorsSchemasBenchmarks
AboutPressPartnersPricingContactLegal
StartEcosystem
White PapersBenchmarksProofsResearch Overview
Explore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself
H33 H33-74 ← All one-pagers Screen-shot the card · Cmd+Shift+4 · paste to LinkedIn
H33
H33-74Chain-Portable Evidence
One-Pager
When Infrastructure Changes

Operational evidence that outlives the system that produced it.

Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.

Assets live on chains. Evidence lives in H33-74.

01

Survives the system

When the platform, vendor, cloud, or chain changes, the proof of every prior approval, transfer, decision, and compliance check stays verifiable. Nothing migrates because nothing was bound.

02

Independently verifiable

An auditor, regulator, or counterparty verifies any individual proof with the open-source verifier. No operator infrastructure required.

03

Post-quantum durable

Three signature families (ML-DSA-65, FALCON-512, SLH-DSA-128f) sign every receipt at the moment of creation. Tampering requires breaking three independent crypto stacks.

Operational Events
AI decisions · Treasury operations · Compliance reporting · Governance evidence · Tokenization actions
Industries
Banking · Insurance · Healthcare · Asset management · Government · AI companies
Regulatory Frameworks Mapped
SOX · DORA · EU AI Act · OSFI B-13 · HIPAA · PCI-DSS · GDPR · NIS2 · FedRAMP · CMMC 2.0
The asset may move.
The evidence remains.
h33.ai/h33-74
H33-74 · Post-Quantum Evidence

H33-74 in brief

H33-74 is the portable 74-byte post-quantum evidence primitive — a 32-byte on-chain commitment plus a 42-byte off-chain receipt, signed under three independent NIST post-quantum signature families (ML-DSA, FALCON, SLH-DSA) — that produces and anchors a self-contained proof of each operational event. It exists because evidence normally dies with the system that made it; H33-74 makes the proof outlive the platform, vendor, cloud, and chain, and stay durable through the quantum transition.

What it is not. H33-74 is a primitive, not a service. It is not continuous monitoring (that is HATS), not the verification verdict (that is Verification), and not AI or workflow governance (that is Agent-008). The blockchain is only an interchangeable anchor — the evidence is never bound to it.

Why does it exist?

Operational evidence is normally bound to the system that produced it and disappears when that system changes. H33-74 makes each proof self-contained and independently verifiable so it outlives the infrastructure.

How is it different from the chain?

The chain holds a 32-byte commitment and is interchangeable. A receipt anchors to one chain, many, or none, and survives migration, deprecation, or a chain disappearing.

What proves it?

Every claim resolves to a reproducible artifact — wire format at /schemas/h33-74/, reproducible timings at /benchmarks/ — checkable with an open offline verifier.

Who owns it?

H33-74 is the ROOT substrate H33 produces and anchors (flagship: /h33-74/). Products like Agent-008, HATS, and PQ-Verified consume it, not redefine it.

Go deeper: What H33-74 is & how it works · How verification works · All role one-pagers