Standard: H33-PQ · Runtime: HATS · Substrate: H33-74
Customers earn the H33-PQ Verified badge. HATS is the engine that keeps it alive — continuously, automatically, and with portable evidence at every cycle.
Most programs answer: “are you post-quantum?” H33-PQ Verified answers: “can you prove it continuously?”
Customers don’t buy compliance platforms because the platforms are the standard. They buy them because they automate the standard. H33-PQ Verified follows the same model.
The customer earns the H33-PQ badge. HATS is the attestation engine underneath. Same as SOC 2 ↔ Drata.
The standard names what gets evaluated. HATS evaluates it continuously. Each substrate layer contributes evidence to the score.
Most certification programs are forms, evidence dumps, annual reviews, and a static badge. H33-PQ Verified replaces the entire loop with continuous machine-generated evidence.
Fill out the questionnaire. Submit evidence. Wait for annual review. Receive badge. Hope nothing breaks between cycles.
HATS continuously evaluates the five pillars. Badge state automatically updates. Portable proof regenerated every cycle. No humans involved at Tier 1.
The word “certified” carries legal and commercial baggage — who certified it? can dead-end a sale. H33-PQ leads with machine-generated evidence and escalates to human review only where buyers require it.
The standard scores the entire trust stack — not just cryptographic algorithms. Each pillar is evaluated continuously by HATS.
A composite score with no breakdown is a black box. H33-PQ Verified always emits the per-pillar score and the primary finding driving the result. Executive-readable by default.
A company can be PQ-compliant today and lose it tomorrow because somebody changed a signing path, introduced a non-PQ dependency, added a new vendor, or deployed a vulnerable agent.
H33-Root governs the authority to make those changes. Every score-affecting change is bound to a delegation chain — H33-PQ Verified + Authority Verified is strictly stronger than H33-PQ Verified alone.
Board-level question: “Who approved the change that reduced our H33-PQ score?”
H33-PQ + H33-Root authority lineage produces a cryptographically verifiable answer. No other post-quantum program does.
The badge is a self-contained block of HTML. No JavaScript dependency. Renders identically on any framework. Score and timestamp update from a tiny JSON endpoint H33 hosts at /api/h33-pq/{customer-id}.json.
<!-- H33-PQ Verified badge — drop anywhere on your site --> <a href="https://h33.ai/standards/post-quantum-verified/?id={your-customer-id}" target="_blank" rel="noopener" data-h33-badge="{your-customer-id}" style="display:inline-flex;align-items:center;gap:12px; padding:12px 18px;background:#0f0f10;border:1.5px solid #C9956C; border-radius:10px;color:#fff;text-decoration:none; font-family:system-ui,sans-serif"> <img src="https://h33.ai/assets/images/h33-badge-logo-32-dark.png" alt="H33" width="30" height="30" style="border-radius:5px"> <div> <div style="font:700 9px/1 monospace;color:#C9956C;letter-spacing:2.5px"> H33-PQ VERIFIED </div> <div data-h33-score>--/100</div> <div style="font:400 10px monospace;color:#aaa">Continuous Attestation</div> <div data-h33-attest style="font:400 10px monospace;color:#888"> Last verified: pending </div> <div style="font:700 9px/1 monospace;color:#666;letter-spacing:1.4px;margin-top:4px"> POWERED BY HATS </div> </div> </a> <script src="https://h33.ai/assets/h33-pq-badge.js" async></script>
The optional h33-pq-badge.js fetches the latest score and timestamp from the customer endpoint every 60 seconds. Without it, the badge still renders — it just shows the last server-rendered state.
For a customer to earn H33-PQ Verified, HATS needs read-access (or telemetry) to evaluate each pillar. None of this is novel infrastructure — instrumentation against existing systems.