Is the HATS artifact shown on this page a real production decision?

No. The artifact on this page is a labeled demo decision with an illustrative subject. Its verdict reads Verified with Signatures Pending because the signing layer is designed but not yet fully demonstrated on this sample.

Why does a HATS proof use triple-family post-quantum signatures?

The artifact is designed to carry post-quantum signatures across the trust path (ML-DSA-87, SLH-DSA-256s, and FALCON/FN-DSA, the latter per the FIPS 206 draft), providing portability and tamper-evidence for the record. This is a property of the evidence record, not a claim that the system is unbreakable.

HATS · PQ-Verified Artifact · Demo

Prove you were protected.

Q: What does a HATS proof establish, and what does it not?

A HATS proof establishes that a HATS-recorded decision occurred as captured and that the artifact reproduces when re-checked. It does not by itself constitute an independent verdict (that is Verification re-checking it), a maturity score (HICS), a governance decision (Agent-008), a security guarantee, or a regulatory-compliance determination. HATS records and monitors operational evidence; it does not verify itself.

Every HATS decision emits a PQ-Verified Artifact — one self-contained file carrying the claim, the verdict, and five attestations. Insurance, compliance, audit, cyber. Drop the artifact into any verifier. Get one answer.

Claim

AI classification decision followed approved policy.

Verdict

Verified · Signatures Pending

Evidence

Governance, Privacy, and Verification attestations validated.

Subject

HATS Demo Decision · Cyber Insurance Continuous Monitoring

Additional Assurances

Cryptography: Triple-family PQ signatures across the trust path (ML-DSA-87 · SLH-DSA-256s · FALCON-1024).
Evidence: Decision artifact is portable and survives the system that produced it.

↓ Download PQ-Verified Artifact Verify Any Artifact →

How it works

01 · HATS decides

A HATS-governed AI decision is made

Policy is enforced at the decision point. Every input, output, and constraint is captured.

02 · Artifact emits

A .h33pqv.json is produced

One file. Five inline attestations. Triple-family PQ signatures over the manifest hash.

03 · Anyone verifies

Drop the file into the verifier

Browser or CLI. Offline. No H33 contact required at any step.

04 · One verdict

Claim, verdict, evidence in one view

Insurers, auditors, regulators see the same thing the AI saw — without taking your word for it.

Pillars under the claim

Three load-bearing for the claim. Two carry it on background.

Load-Bearing

Governance

5-level authority lineage with monotonic narrowing — the policy that governed the decision.

Load-Bearing

Privacy

Encrypted-input processing under H33 CKKS-256 — sensitive features never exposed in plaintext.

Load-Bearing

Verification

Open-source h33-pq-verify replays the decision offline.

Background

Cryptography

PQ stack: ML-DSA-87 · SLH-DSA-256s · FALCON-1024 · ML-KEM-1024 · NIST L1/L3/L5.

Background

Evidence

Portable evidence chain — the decision survives the system that produced it.

Want HATS emitting artifacts in your stack?

HATS-governed decisions can produce a PQ-Verified Artifact per decision, per shift, per cycle, per audit window. Insurers, brokers, and compliance owners get one file instead of a screenshot pack.

See HATS Live Demos →

What a HATS proof is — and is not. A HATS proof is the portable artifact of HATS's owned role: HATS records and monitors operational evidence over time, and this file is the record made portable — the claim, the captured decision, and the attestations, in one .h33pqv.json. It establishes that a HATS-recorded decision occurred as captured and that the artifact reproduces. It does not render the independent verdict itself — that is Verification, done by an offline verifier re-checking this artifact; it is not a maturity score (HICS); and it is not the governance decision (Agent-008). The artifact carries the record so an independent party can verify it — HATS does not verify itself.

Why the artifact exists — and when not to use it

A screenshot pack asserts protection; a HATS proof lets anyone reproduce it. The artifact exists so continuous operational evidence travels beyond the system that produced it and can be re-checked offline after the fact. When a HATS proof is not the right thing: if you need the independent verdict rendered on the artifact, run Verification (the artifact is the input, not the verdict); if you need a single maturity grade, that is HICS; if you need to control what a decision is allowed to do, that is Agent-008. Do not treat downloading a HATS proof as having independently verified it.

Decision guidance: route the right tool

Use HATS when the requirement is continuous operational evidence recorded over time — and this proof when you need that evidence as a portable, re-checkable file.
Use Verification when the requirement is an independent verdict on this existing artifact. Do not treat HATS monitoring or holding a proof as independent verification — the verifier renders the verdict; HATS supplies the record.
Use HICS when the requirement is a maturity score.
Use Agent-008 when the requirement is to govern a decision; HATS then records that the governance held.

Frequently asked

What does a HATS proof establish — and what does it not?
It establishes that a HATS-recorded decision occurred as captured and that the artifact reproduces when re-checked. It does not by itself constitute an independent verdict (that is Verification re-checking it), a maturity score (HICS), a governance decision (Agent-008), a security guarantee, or a regulatory-compliance determination.

If I hold the artifact, is it already verified?
No. Holding the file is not verifying it. Verification happens when an independent verifier re-checks the artifact offline and renders a verdict. HATS records and monitors; it does not render that verdict.

Is the artifact shown here from a real production decision?
No. The artifact on this page is a labeled demo decision with an illustrative subject; its verdict pill reads “Verified · Signatures Pending” because the signing layer is designed but not yet fully demonstrated on this sample.

Why triple-family PQ signatures?
The artifact is designed to carry post-quantum signatures across the trust path (ML-DSA-87, SLH-DSA-256s, and FALCON/FN-DSA, the latter per the FIPS 206 draft). This is a portability and tamper-evidence property of the record, not a claim that the system is unbreakable.