Normative technical documents for the H33 attestation infrastructure. These specifications use RFC 2119 conformance language and are intended for implementers, auditors, independent verifiers, and regulators. They are not marketing materials.
What this hub is. A directory of the normative specifications that define the H33 attestation infrastructure — the wire formats, algorithms, and conformance requirements an implementer needs to produce and verify H33 evidence independently of H33 infrastructure. It defines no format itself; each linked document is the authority for its own concept.
Boundary. These are specifications, not runtime. They do not render verdicts on real artifacts (that is independent verification), do not monitor operational evidence over time (that is HATS, which records and monitors), do not score software maturity (that is HICS), and do not govern AI decisions at runtime (that is Agent-008). The primitive these documents describe and bind is produced and anchored by H33-74.
Defines the 74-byte fixed-width post-quantum attestation primitive. Covers the byte layout (32 bytes on-chain commitment + 42 bytes cached receipt), computation type enumeration, three-family PQ signature binding, chain anchoring procedures for Bitcoin (Taproot), Solana (memo), and Ethereum (calldata), and independent verification steps.
Defines the full attestation receipt JSON structure including receipt identity, input/output commitments, policy and authority hashes, chain linking via predecessor hashes, three-family PQ signature bundles, and the canonical hash computation rules (NFC normalization, little-endian encoding, length-prefixed fields, domain separators). Includes formal JSON Schema and worked examples.
Defines the directed acyclic graph (DAG) structure for attested governance decisions. Covers 8 node types (Route, Policy, Event, Result, StateTransition, Checkpoint, Federation, Anchor), edge semantics, Merkle root computation over BTreeMap-ordered nodes, deterministic replay semantics, canonical replay frames, integrity classification levels (INTACT, PARTIAL, DIVERGENT, BROKEN), and the relationship to HATS Section 4.
Defines binding of an attestation with signatures from three independent post-quantum families rooted in distinct hardness assumptions: ML-DSA-65 (FIPS 204, MLWE), FALCON-512 (NTRU lattice), and SLH-DSA-SHA2-128f (FIPS 205, hash-based). Specifies the signature bundle byte layout, the digest-first signing algorithm, and an AND-gate verification requirement: a bundle is valid only if all three families verify. There is no 2-of-3 mode.
Defines how autonomous AI agent decisions are bound to attested, replayable evidence so that policy and decision integrity can be checked after the fact. Covers the decision record structure, the binding of each governed action to its policy and authority context, and the relationship to the Agent-008 governance layers. Governs the record format; the runtime enforcement of policy is Agent-008.
Defines a deterministic score derived from recorded operational-integrity evidence — the inputs, the weighting, and the computation rules that map evidence to a reproducible number. OIS quantifies operational-integrity state from HATS-recorded evidence; it does not itself monitor systems (that is HATS) and does not score software maturity against a development rubric (that is HICS).
They are normative documents for the H33 attestation infrastructure: the H33-74 primitive, the attestation receipt schema, the multi-family post-quantum signature framework, the AI agent governance attestation model, the governance proof model, and the Operational Integrity Score. Each defines wire formats, algorithms, and conformance requirements in RFC 2119 language.
This index is a directory only and defines no format itself. Deployment guides, pricing, and SLAs live elsewhere. Independent verification verdicts on real artifacts are rendered by the verification surface, not by these normative documents.
H33-74 produces and anchors the portable 74-byte post-quantum evidence primitive these documents describe, bind, and extend. The receipt schema, multi-family PQ framework, and governance proof model reference that primitive as their common substrate.
A specification defines a format or algorithm normatively. HATS records and monitors operational evidence over time; the verification surface renders the independent verdict on a specific artifact; HICS scores software maturity; Agent-008 governs AI policy and decision integrity. A spec is the normative reference these consume.