Related · tier-1 reading. For how an auditor verifies this independently, see Independent Verification.
Six encyclopedic explainers. No hand-waving. Each covers the full technical pipeline from first principles through production architecture, with real performance numbers from measured systems.
Every mechanism below shares one organizing principle: it produces evidence that is independently verifiable and anchored to H33-74, the 74-byte post-quantum attestation primitive H33 produces. Attestation, agent governance, encrypted computation, integrity scoring, and replay are different operations, but each emits the same portable proof, so an outsider can check any result without trusting the operator. This hub explains the mechanisms; H33-74 is the primitive they all anchor to, and independent verification is how anyone confirms them.
Each explainer is self-contained. Read them in any order. They cross-reference each other where architectural dependencies exist.
The attestation pipeline from state change detection through hash computation, PQ signature, chain extension, and on-chain anchor. Why periodic audits leave gaps that continuous attestation eliminates.
Agents act faster than humans audit. Every agent action becomes a node in a cryptographic execution DAG. Scope enforcement, negative authority proofs, and deterministic replay at any timestamp.
Compute on ciphertext without decrypting. Prove the computation was correct without revealing inputs. BFV, CKKS, TFHE unified under a single 74-byte attestation model with STARK integrity proofs.
Six dimensions. Weighted composite scoring. Degradation detection. Recovery tracking. A continuous numerical signal that tells you whether your governance infrastructure is actually functioning.
Deterministic reconstruction from cryptographic evidence. DAG traversal, state reconstruction, frame hashing. Replay any timestamp. Detect any tampering. Fork to explore counterfactuals.
Harvest now, decrypt later applies to governance evidence, not just encrypted data. Three independent hardness assumptions. NIST FIPS 203/204/205. No performance tradeoff.
Six technical explainers covering the cryptographic mechanisms behind H33: continuous attestation, provable AI agent governance, verified encrypted computation, operational integrity scoring, governance replay, and post-quantum attestation. Each mechanism produces independently verifiable evidence anchored to H33-74, the 74-byte post-quantum attestation primitive.
Every mechanism emits evidence that is independently verifiable and anchored to the same 74-byte post-quantum attestation. Different operations produce the same portable proof, so an outsider can check any result without trusting the operator.
Any order. Each is self-contained and cross-references the others where dependencies exist. A common path: continuous attestation first (how evidence is produced), then agent governance and encrypted computation (what produces evidence), then operational integrity and replay (how evidence is measured and reconstructed).
Every mechanism is designed so an independent party can verify the evidence without trusting H33, using the H33-74 attestation and the independent verification path. The explainers cite measured performance numbers from production hardware, not theoretical peaks.
These explainers describe what H33 does. The research section explains why the alternatives fail.