H33 attests itself first under H33-PQ Verified.
A standard without an attested operator is a proposal. H33 is running the first self-attestation cycle against H33-PQ Verified — the acceptance gate that recognizes post-quantum conformance — publishing evidence as it lands, and exposing verification commands so any third party can replay the result offline. This is the live page, and this attestation is self-asserted by H33, not independently certified: PQ-Verified recognizes conformance to a published gate, and here H33 is both the operator and the applicant. Status, bundles, and pass/fail per pillar update every attestation cycle. No badge is claimed until all five pillars verify clean.
Five Pillars · Five Bundles · One Verification Path
Each pillar produces one or more public artifacts and a public verification command. Anyone can replay the result without contact with H33.
Evidence artifacts that survive H33.
H33 produces portable evidence bundles for every regulated-domain decision. Each bundle is independently verifiable using the open-source h33-verifier CLI, without contact with the H33 runtime, the H33 cloud, or any participating subsystem.
Every action traces back to original human intent.
Every authority decision H33 makes carries a cryptographically provable lineage from the leaf action back to the root authorization. Ancestor constraints inherit downward; revocation propagates downward; intent is preserved across arbitrary delegation depth.
Sensitive computation happens on encrypted data.
H33 declares the data_access_mode for every sensitive computation. Where the declaration is encrypted, an independent FHE verifier confirms that no plaintext access occurred. Where the declaration is plaintext, the privacy posture is explicit and verifiable.
Anyone replays the result. Offline.
Every bundle on this page can be replayed by any third party using the open-source h33-verifier CLI. No contact with H33 required. No subsystem dependency. The verifier itself is reproducible from source under Apache-2.0.
h33-verifier --version
h33-verifier verify-conformance
Triple-family PQ across the entire trust path.
Every cryptographic binding produced by H33 — root signature, delegation node signature, revocation signature, replay attestation — is signed under NIST post-quantum algorithms: ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) are finalized; FALCON (FN-DSA / FIPS 206) is still a draft. Triple-family algorithm diversity (ML-DSA + SLH-DSA + FALCON) at the root level, and acceptance is an AND-gate — an attestation is conformant only when all three families validate (3-of-3, never 2-of-3). NIST Security Levels 1, 3, and 5.
One command. Five pillars. Offline.
The master verification command pulls every bundle from this page, runs every pillar's verification offline against the open h33-verifier, and prints PASS or FAIL per pillar. No contact with H33 is required at any step.
h33-verifier attest \
--target https://h33.ai/pq-verified/h33-self-attestation/ \
--standard h33-pq-verified-v1.0 \
--output report.json
Note: the master attest subcommand ships in h33-verifier 0.2.0 as part of this self-attestation program. The per-pillar verification commands above work today against h33-verifier 0.1.0.
This page reflects the actual state of H33's self-attestation cycle. Pillars 4 (Independent Verification) and 5 (Post-Quantum Security) have all artifacts ready and verifying clean. Pillars 1, 2, and 3 are in the publishing phase of the current cycle — some bundles are live, some are being assembled and signed under the H33 release keys. This page updates as bundles publish. The H33-PQ Verified homepage badge is withheld from h33.ai until all five pillars verify clean — a badge without proof is marketing, a badge with downloadable evidence is a demonstration.
This self-attestation is one expression of the H33-PQ Verified acceptance gate, which recognizes post-quantum conformance. The evidence it references lives in the standard's own artifacts: