Machine-readable schema definitions for H33 attestation, governance, and verification payloads. All schemas include canonical examples, failure modes, and verification procedures.
These schemas are intended for consumption by automated systems, CI/CD pipelines, independent verifiers, and any tooling that produces or validates H33 payloads. Each schema is a self-contained reference document with field definitions, cryptographic assumptions, encoding rules, and conformance requirements.
JSON Schema for HATS attestation payloads. Defines the governance graph, root hash, signer set, verification status, and proof profile fields required to represent a complete HATS attestation record.
JSON Schema for the H33-74 74-byte attestation receipt. Defines the binary-to-JSON mapping, anchor commitment, cached receipt fields, computation types, and encoding rules for API transport.
JSON Schema for governance proof bundles. Defines the full governance graph structure, replay frames, signature bundles, and verification manifests required for independent governance verification.
JSON Schema for Operational Integrity Score payloads. Defines the six-dimension scoring model, weight vectors, degradation and recovery event arrays, and threshold interpretation rules.
JSON Schema for the output of hats verify or any conformant verifier. Defines status enumerations, chain integrity, replay results, failure objects, and CLI output mapping.
A schema is the machine-readable contract for a portable evidence payload — the receipt or attestation H33-74 produces. It is the evidence artifact's definition, not the verdict on it. Validating against a schema is not the independent verdict (Verification), not operational monitoring (HATS), and not the governance decision (Agent-008).
H33-74 produces the payload these schemas describe; Verification independently renders the verdict on it. Schema validation confirms a payload is well-formed and re-checkable; deciding whether the evidence should be trusted, against policy, is Verification's role on a separate axis.
Offline, by anyone, trusting no one. A verifier validates the payload against its published schema (JSON Schema draft 2020-12) and re-checks its declared hashes — SHA3-256 commitments and CRC checksums — on an air-gapped machine. Any changed byte breaks a check, so the result is tamper-evident. No H33 API key or connectivity is required. The signature families the payloads carry (ML-DSA, FALCON, SLH-DSA) are external NIST-track standards H33 implements.
Whenever you need to produce or independently validate portable, offline-verifiable proof that survives infrastructure and time — for CI/CD conformance, third-party verifiers, or auditors who must confirm a record without contacting H33.