Every meeting ships a receipt. Tamper one byte — it rejects.
H33 Session produces a portable .h33pqv.json receipt that proves a session happened exactly the way it was supposed to. The receipt is the product. Triple-family post-quantum signatures (ML-DSA-87 · SLH-DSA-256s · FALCON-1024) verify in two seconds. Zero metadata leak.
The verifier runs in the browser. No login, no account, no sales call. Drop a receipt → PERMIT or REJECT. Modify one byte → REJECT. That's the whole contract.
The live break
Receipt + tamper buttonSame artifact. Same verifier. One bit changes the verdict.
Paste a Zoom, Teams, or Google Meet calendar invite. Count the metadata fields it exposes — subject, attendees, organizer, recurrence, vendor extensions. Compare to what H33 Session reveals instead.
Measure your current leak ›Drop any H33 Session .h33pqv.json receipt into the verifier. Triple-family post-quantum verification. PERMIT or REJECT in two seconds. No login, no account, no sales call.
Why the receipt holds
Triple-family post-quantum signatures
Every receipt is signed under ML-DSA-87 (lattice), SLH-DSA-256s (hash), and FALCON-1024 (NTRU). A break in any one family does not break the receipt — all three must verify. No PLONK, Groth16, BLS, KZG, or pairings anywhere in the stack.
Zero metadata leak
Zoom, Teams, and Meet calendar invites leak ~17 fields per invite — subject, attendees, organizer, recurrence pattern, vendor extensions. The H33 Session envelope strips that surface to zero before the receipt is signed.
The receipt IS the product
Not a dashboard. Not a search index. Not a vendor contract you depend on. One .h33pqv.json file, portable forever, verifiable in the browser without us. That's the product.
Where H33 Session sits in the stack
H33 Session is the meeting-layer surface of the H33 substrate. The receipt is emitted by a HATS gate after the substrate validates the three authority bindings (authority · instruction · execution). The same gate that produces a receipt for a meeting produces a receipt for an agent decision, a tokenization event, or a compliance proof — same envelope, same verifier, same artifact format.
Application guarantee: no authorized session executes twice · Substrate guarantee: no actor receives authority from anything not bound to them and valid at session start.