Post-Quantum Evidence · Measured · Reproducible

The proof is heavy. The handle is 74 bytes.

A single governed decision carries ~37 KB of post-quantum evidence. H33-74 collapses the part that has to travel to a 74-byte attested handle — ~500× — while the full proof stays intact and independently verifiable in the evidence graph. Not compression. Virtualization.

74 B

portable handle
32-byte anchor + 42-byte binding

~500×

transport reduction
~37 KB → 74 B

7/7 · 9/9 · 3/3

proof suites, fail-closed
real PostgreSQL + L5 triple-PQ

~34 KB

proof retained
irreducible, verifiable floor

The measured byte collapse

What has to travel per decision, across the committed experiments. The ~34 KB signature isn’t shrunk — it’s retained in full and referred to. Only the transport/index representation collapses.

Full evidence bundle~461 B fields + ~34 KB triple-PQ sig + ~1,466 B self-attest

~37 KB

1× baseline

Decision projection envelopefirst compact index

763 B

~49×

Reduced core (JSON)4 of 10 fields recovered from the graph · 8f2852b5c

300 B

~123×

Native core (framed)signed commitment reconstructed, not carried · 8f2852b5c

228 B

~162×

Commitment tierSHA3-384 the attestation binds

48 B

tier

H33-74 portable object32-byte anchor + 42-byte binding, 3-PQ-key attested · af17f1f98

74 B

~500×

bar length = log₁₀(bytes) · the 34 KB signature stays whole in the graph

Preserved once

~34 KB

full triple-PQ proof — retained, content-addressed, independently verifiable. Nothing discarded.

~500×commits to
& recovers

Travels everywhere

74 B

attested handle carried through APIs, audit, ledgers, agents — the proof stays put.

Recovered, not carried — the lossless claim

Of the 10 fields in the 763 B envelope, these no longer travel — they are pure functions of the bundled attestation or the content-addressed graph, proven byte-for-byte.

keyset_ref

recovered from att

suite_id

recovered from att

self_attestation_digest

recovered from att

bind_provenance_root

recovered from att

canonical_commitment 929b1021d

byte-identically reconstructed from the content-addressed graph over the full authority event, matched to the original signed value — it no longer travels.

The ~34 KB triple-PQ proof is retained in the store and re-verified on replay. Nothing is compressed or discarded — virtualization, not signature compression. There is no lossy-crypto claim to attack.

What the 74 bytes determine

The handle binds a 48-byte SHA3-384 evidence root over the minimum coordinate tuple — recovered from the store and re-verified against the root, with no external constant supplied by the verifier (7/7, af17f1f98).

decision_id

which authorization this is

evidence_digest

content-address of the full proof (identity, not a locator)

authority_service_identity

committed & recovered — not supplied (the 228 B gap, now closed)

canonical_type_id

the semantic version

accepted_evidence_kind

the semantic kind

pq_time_root (optional)

binds the temporal-continuity evidence

A cryptographic boundary, not a pointer

Every case fails closed from the 74-byte object alone — proven on real PostgreSQL with real triple-PQ signatures.

Wrong service identityroot mismatch

FAILS CLOSED

Wrong version / evidence kindroot mismatch

FAILS CLOSED

Swapped evidence graphdigest repointed

FAILS CLOSED

Cross-decision mixA’s object → B’s evidence

FAILS CLOSED

PQ-Time substitutionwhen enabled

FAILS CLOSED

Corrupt evidence bytescontent-address mismatch

FAILS CLOSED

Missing / dangling evidenceunresolved

FAILS CLOSED

Forged DecisionIdreconstruction mismatch

FAILS CLOSED

Tampered commitmentpreimage altered

SIGNATURE FAILS

v1 historical forced into v2not rewritten

REFUSED

How recovery works

Given only the root and the substrate — nothing else:

Recover the coordinate record and re-hash it against the root (mismatch → fail closed).

Fetch the full evidence by its committed digest — an identity, never a storage locator.

Reconstruct the byte-identical signed commitment from the recovered coordinates.

Verify the real triple-PQ signature — ML-DSA-87 + FALCON-512 + SLH-DSA-256s, 2-of-3.

Confirm the full ~34 KB proof still verifies independently — nothing was discarded.

One primitive, many governed uses

Domain separation is proven (3/3, cca039f15): the same tuple under a different profile yields a different root. A handle minted for authorization can never be reinterpreted as another kind of evidence.

H33-74 / AuthorizationEvidenceRoot / v1≠ IdentityEvidenceRootTransactionEvidenceRoot AgentExecutionEvidenceRootComplianceEvidenceRoot

At scale — and it dedups too

1B governed events: ~37 TB proof-in-motion → ~74 GB of handles

Full proofs stay verifiable on demand. Storage dedups independently: the ~1,466 B authority context is content-addressed once per authority, not per decision — in a 150-decision corpus, 5 shared objects backed all 150, removing ~1,477 B/decision of re-carried context; the ~34 KB signature is the irreducible floor. Soak at N=150: projection, retrieval, and full PQ-replay latencies stay flat (p50/p95/p99) — verification doesn’t degrade with corpus size.

The future of cryptography is heavier. The proof doesn’t have to be.

H33-74 is the portable, post-quantum-attested commitment to heavyweight governed evidence — while the complete proof stays intact behind it.

Explore H33-74 →

Reproducibility — every figure is backed by a committed suite (real PostgreSQL + real L5 triple-PQ):

• decision_core_pg_proofs 9/9 — 763→228, byte-identical reconstruction, replay-equivalence, fail-closed, cross-decision isolation 8f2852b5c 929b1021d

• authorization_evidence_root_pg_proofs 7/7 — root-alone determination, no external constant, full attack matrix af17f1f98

• profile domain-separation 3/3 cca039f15 • decision_projection proofs + soak (N=150) — boundary, envelope, dedup, flat latency

Suite: ML-DSA-87 (L5) + FALCON-512 + SLH-DSA-256s (L5), 2-of-3 · evidence root SHA3-384 (48 B) · corpus N=150 across 5 authority instances. “74 B” is spec-defined (32-anchor + 42-binding), not a serialized wire measurement; it binds to the retained ~37 KB proof.