Every H33 research artifact in one place. The Research Program tracks papers in progress. Whitepapers and specifications define the substrate. Research Essays argue why the conventional security model is structurally insufficient.
The five artifacts most likely to be useful on a first visit.
The technical paper underpinning how authority survives rotation, recovery, and revocation. The load-bearing artifact for H33's "authority survives" thesis.
The 74-byte post-quantum attestation envelope: structure, signature families, verification path, and conformance corpus.
Empirical research on why governance systems fail in multi-agent delegation chains. Four papers in flight, one in validation.
Post-quantum signature standard with three signature families (ML-DSA-65, FALCON-512, SLH-DSA). Available as .md, .pdf, and .docx.
The H33 AI Trust Standard specification. Conformance suite, verification guarantees, and architecture.
The H33 Research Program ships empirical papers tied to load-bearing claims in the cryptographic substrate. Status is updated as papers move from drafting through validation to distribution.
Paper 1. Empirical measurement of governance failure modes in multi-agent delegation chains. Benchmark run underway.
Paper 2. How offline-verifiable evidence outlasts vendor disappearance and platform migration. Currently in drafting.
Paper 3. Authority Transfer, Ratification Chain, and Pre-Cert Conflict Resolution as primitives. Currently in drafting.
The substrate paper. Active distribution to design partners and the cohort.
Canonical technical documents defining the substrate, standards, security parameters, and patent portfolio.
The 74-byte post-quantum attestation envelope and portability layer.
How authority survives rotation, recovery, and revocation. The substrate is the H33 contribution; Agent-008 is its deployed form. (HTML + PDF)
Post-quantum signature standard. ML-DSA-65, FALCON-512, SLH-DSA.
H33 AI Trust Standard. Conformance + verification + architecture.
The 9-patent / 250+-claim portfolio. Authority Transfer, VintageBinding, Ratification Chain.
Concrete parameter sets, security levels, and rationale for every primitive.
FHE, ZK, and the cryptographic services stack.
Each essay presents a strong technical thesis, a structural analysis of why the conventional approach fails, and a comparison with cryptographic alternatives. These are architectural arguments, not opinion pieces.
Self-reported questionnaires and log aggregation are governance in name only. Without independent verification, governance is a claim, not evidence.
Logs describe events. They do not prove them. The gap between "we logged it" and "you can independently verify it" is the gap between governance theater and actual governance.
SIEM aggregates and correlates logs. It does not verify them. Observability is not reproducibility. Monitoring is not proof.
SOC 2 is periodic, sampling-based, and built on self-selected evidence. Continuous attestation is exhaustive, tamper-evident, and independently verifiable.
Tokenization proves ownership. It does not prove operational integrity, compliance state, or data non-exposure.
The papers explain. The substrate runs in production. The verifier proves it independently.