Which one-pager should a given executive read?

Start with the buyer's own concern: CFO for audit horizon and vendor portability, CISO for tamper-evident SIEM-independent audit, CCO for regulatory crosswalks, CIO/CTO for chain and infrastructure portability, General Counsel for litigation and regulator evidence, and Chief Trust Officer for AI decision and agent-action auditability. Each frames the same H33-74 primitive for that role.

How is H33-74 different from the blockchain it anchors to?

The blockchain is an interchangeable notarization anchor holding a 32-byte commitment. The evidence is never bound to any chain, so it survives chain migration, deprecation, or a chain disappearing.

What evidence supports H33-74?

Every claim resolves to a reproducible artifact: byte-exact wire format at /schemas/h33-74/ and signing and verification timings at /benchmarks/, both independently reproducible with an open offline verifier.

Who owns the H33-74 primitive?

H33-74 is the ROOT substrate H33 produces and anchors; the flagship reference is at /h33-74/. Products such as Agent-008, HATS, and PQ-Verified consume it rather than redefine it.

H33-74 One-Pagers

Q: What is H33-74?

H33-74 is the portable 74-byte post-quantum evidence primitive: a 32-byte on-chain commitment plus a 42-byte off-chain receipt, signed under three independent NIST post-quantum signature families (ML-DSA, FALCON, SLH-DSA). It produces and anchors one self-contained proof per operational event, and is a fixed-size primitive rather than a product or service.

Q: What does H33-74 not do?

H33-74 is the evidence primitive only. It is not continuous monitoring (that is HATS), not the verification verdict (that is Verification), and not AI or workflow governance (that is Agent-008). It produces and anchors the proof; the higher-level products build on it.

What every one of these one-pagers is about

H33-74 is the portable 74-byte post-quantum evidence primitive — a 32-byte on-chain commitment plus a 42-byte off-chain receipt, signed under three independent NIST post-quantum signature families (ML-DSA, FALCON, SLH-DSA) — that produces and anchors a self-contained proof of each operational event. It is a fixed-size primitive other systems build on, not a product or service. Every card below frames the same primitive for one buyer's concern.

What it is not. H33-74 is not continuous monitoring (that is HATS), not the verification verdict (that is Verification), and not AI or workflow governance (that is Agent-008). The blockchain is only an interchangeable anchor — the evidence is never bound to it. See the flagship: what H33-74 is & how it works.

Universal Master

Operational evidence that outlives infrastructure

The whole story in one page. Three properties. Ten frameworks. Six industries. Five operational categories.

Open master →

Role-based one-pagers

Each one targets a specific budget owner with the language and concerns that role responds to.

For CFOs

Treasury operations, audit horizon, vendor portability

"How much audit history will we lose when we change chains, providers, or platforms?"

Open one-pager → For CISOs

SIEM-independent audit, tamper-evident, post-quantum

"My audit evidence depends on the SIEM staying up. My logs depend on me not being compromised."

Open one-pager → For CCOs

Ten regulatory crosswalks, auditor-direct verification

"Every audit cycle requires reconstructing controls from systems we no longer run."

Open one-pager → For CIOs & CTOs

Chain portability, infrastructure independence

"Vendor and chain decisions become architectural commitments we can't reverse."

Open one-pager → For General Counsels

Litigation evidence, regulator inquiry, D&O

"Producing operational evidence years after the system was replaced."

Open one-pager → For Chief Trust Officers

EU AI Act Article 12, agent attestation, model-portable

"Model provider change loses the audit trail for every prior decision."

Open one-pager →

How to use these for LinkedIn

Open the one-pager in a browser. The card itself is exactly 1080 × 1350 pixels — LinkedIn's recommended 4:5 vertical aspect ratio.
On macOS: Cmd + Shift + 4, then drag a rectangle around the card. The screenshot is saved to Desktop ready for upload.
On Windows: Win + Shift + S for Snipping Tool, then select the card.
Drop the image directly into a LinkedIn post. The card was sized so the 4:5 ratio renders edge-to-edge on mobile.
Print to PDF (Cmd + P → Save as PDF) for sales attachments. The print stylesheet hides the top bar so the PDF is a single clean page.

Questions these one-pagers answer

Which one-pager fits a given buyer?

Match the concern: CFO for audit horizon and vendor portability, CISO for tamper-evident SIEM-independent audit, CCO for regulatory crosswalks, CIO/CTO for chain and infrastructure independence, General Counsel for litigation and regulator evidence, Chief Trust Officer for AI decision and agent-action auditability.

How is H33-74 different from the chain it anchors to?

The chain is an interchangeable anchor holding a 32-byte commitment; the evidence is never bound to it and survives chain migration or deprecation.

What proves it?

Every claim resolves to a reproducible artifact — wire format at /schemas/h33-74/, reproducible timings at /benchmarks/, checkable with an open offline verifier.

Who owns it?

H33-74 is the ROOT substrate H33 produces and anchors (flagship: /h33-74/). Products like Agent-008, HATS, and PQ-Verified consume it, not redefine it.

Go deeper: What H33-74 is & how it works · How verification works · Universal master one-pager