HATS Verified
Continuous Verification Active
ML-DSA-65
FALCON-512
SLH-DSA
This badge is cryptographically attested. The verification state below is signed by three independent post-quantum signature families.
Tenant
—
Verification State
VERIFIED
CRV (Verification Score)
87
Controls Verified
6 / 6
Continuous Since
47 days
Last Attested
—
Proof ID
—
On-Chain Hash
—
PQ Signatures
3 families verified
Deterministic
true — reproducible at any time T
Embed This Badge
Add this to proposals, emails, or websites. The badge links to this live verification page.
<a href="https://h33.ai/hats/badge/?tenant=demo"><img src="https://h33.ai/hats/badge/verified.svg" alt="HATS Verified" height="40"></a>
Click to copy
HATS · Records operational evidence
What this badge is — and isn't
Definition. The HATS badge is a portable projection of a HATS record: HATS records and monitors the operational evidence that declared controls kept operating, over time, and the badge points to that record. It is not a verdict, a score, or a governance decision. Verification renders the independent verdict on an existing artifact; HICS assigns a maturity score; Agent-008 governs an AI agent's decision. The badge only shows what HATS recorded.
What the badge attests vs. what it does not
It attests
Which declared controls were observed operating, the continuous verification signal (CRV), how long observation has been continuous, bound so the underlying record is tamper-evident and reproducible.
It does not attest
That a system is secure, that no breach occurred, that a claim will be paid, or an independent verdict. HATS records evidence; it does not verify itself, price, or determine compliance.
Why the badge is a HATS surface, not a Verification surface
A badge that quietly implied “independently verified” would blur two roles. HATS exists to keep a continuous, reproducible record of operational evidence; Verification exists to render an independent verdict on an artifact that already exists. The badge is the portable face of the HATS record — so anyone can find and re-check the evidence — while the independent verdict lives at Verification. Keeping them separate is what makes the evidence trustworthy: the record never proves itself.
Which H33 component do I actually need?
Use the HATS badge for a portable, continuously updated signal of recorded operational evidence.
Use Verification for an
independent verdict on an existing artifact — not monitoring, and not what the badge provides.
Use HICS for a
maturity score of a program.
Use Agent-008 to
govern an AI agent's decision.
FAQ
What exactly does the badge attest?
Observed operational state that HATS recorded: controls seen operating, the CRV signal, and continuous observation duration — cryptographically bound so the record is tamper-evident and reproducible.
What does the badge NOT attest?
It does not claim a system is secure, that no breach happened, or that an insurer will pay. HATS does not determine pricing, coverage, or regulatory compliance — interpretation is external to HATS.
Is the badge an independent verification?
No. It is a HATS-recorded evidence signal. An independent, offline verdict that the underlying artifact reproduces is a separate step performed by
Verification.
How is the badge different from Verification?
The badge is HATS recording and showing operational evidence over time. Verification is an independent verdict on an artifact that already exists. The badge points to the record; Verification renders the verdict on it.
Owner: HATS standard (records/monitors operational evidence) · Evidence anchored on H33-74 · Independent verdict via Verification · Maturity score via HICS · AI-decision governance via Agent-008.