Explore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself
HATS Standard — Draft v1.0
HATS Standard · Layer 7 H33-TRUTHSee how replayable verification works end-to-end →

Replay-Grade
Governance Infrastructure

HATS is an open governance and replay protocol for independently verifiable operational evidence. Any system. Any verifier. Deterministic outputs. Forever.

Current Version 1.0.0
Status Draft
Editor Eric Beans
PQ Profile HATS-PROFILE-PQ-SHA3-256-v1
Verification Pipeline
Input System
Structure Governance Graph
Evidence Replay
Output Independent Verification
Protocol Properties

What HATS Guarantees

HATS is a publicly available technical conformance standard for continuous AI trustworthiness; certification under HATS provides independently verifiable evidence that a system satisfies the standard's defined controls.

Architecture

Governance as Deterministic Infrastructure

HATS treats governance not as documentation but as a deterministic system with defined inputs, reproducible outputs, and machine-testable conformance.

LayerFunctionProperty
Governance Graph Structured representation of policies, controls, and authority bindings deterministic
Replay Engine Reconstructs verification state from governance graph and evidence bundle reproducible
Rejection Semantics Stable error codes, severity classification, requirement references frozen
Transcript Binding Canonical encoding and hash derivation for all verification artifacts immutable
PQ Attestation Post-quantum signatures over governance state and verification outputs quantum-resistant

Governance reconstruction does not require trust in the original signing authority. The verification bundle is the evidence. The replayer is the judge.

Conformance

Machine-Testable. Not Self-Asserted.

HATS conformance is a test result, not a marketing claim. Canonical vectors define byte-identical expected outputs for every verification path.

$ hats-verify conformance --vectors ./hats-v1.0.0/ --profile PQ-SHA3-256

PASS  26/26 canonical vectors
PASS  transcript derivation
PASS  rejection semantics (all 26 error codes)
PASS  replay integrity classification
PASS  domain separator consistency

Profile: HATS-PROFILE-PQ-SHA3-256-v1
Result: CONFORMANT
ImplementationLanguageVectorsStatus
H33 Reference Rust 26/26 Conformant
Your implementation Register
Documentation

Read the Standard

The HATS standard is defined across six documents. Each addresses a distinct verification concern.

Core Document
Specification
The complete HATS protocol specification. Requirements, data models, verification semantics, error taxonomy, proof profiles.
Verification
Verification Guarantees
What HATS verification proves. Deterministic properties, replay integrity levels, and the boundary between verified and unverified claims.
Testing
Conformance Suite
26 canonical test vectors. Byte-identical expected outputs. Machine-verifiable conformance for any implementation in any language.
Stability
Protocol Stability
Frozen surfaces, compatibility rules, and version governance. What can change, what cannot, and what requires a breaking version.
Concept
Replay-Grade Evidence
What "replay-grade" means. The distinction between attestation, audit, and independently reconstructible verification evidence.
Tooling
Verifier CLI
Download the reference verifier. Run conformance checks locally. Validate governance bundles against the canonical test vectors.
Rejection Semantics

Deterministic Failure

Non-conformant governance does not silently degrade. It fails with stable error codes, severity classification, requirement traceability, and replay integrity grading.

{
  "error": "HATS_ERR_POLICY_EXPIRED",
  "severity": "critical",
  "requirement": "REQ-1.3",
  "replay_integrity": "deterministic",
  "rejection_class": "policy_violation",
  "deterministic": true
}
Ecosystem

Independent Implementations Welcome

HATS is defined by its specification and canonical vectors, not by any single codebase. Third-party implementations can validate protocol equivalence without trusting H33 infrastructure.

Contact standard@h33.ai to register your implementation for conformance certification.

Rust-native cryptography. Language-neutral verification.

The H33 reference implementation is pure Rust. The cryptographic hot path does not depend on JavaScript or browser runtimes. Proving, verification, transcript construction, field arithmetic, and challenge derivation execute without any scripting layer.

Portable JSON test vectors allow independent verifiers in Go, TypeScript, Python, Java, or Rust to reproduce identical outputs. The verification path is fully deterministic and backed by canonical conformance vectors for third-party reimplementation.

Verify the Protocol Yourself

Download the canonical test vectors. Run the reference verifier. Build your own implementation. The protocol is the proof.

Read the Specification Download Verifier CLI