How do the artifacts agree without contacting H33?

The Portable Attestation is half of a four-artifact loop: the bundle it refers to, the attestation, and the H33 Portability Verifier binary. The verifier checks all three; any tampering at any layer flips the verdict to FAIL.

Which post-quantum signatures sign each attestation?

Three post-quantum families sign every attestation: ML-DSA-65 + FALCON-512 + SLH-DSA-128f on the commercial path, and ML-DSA-87 + SLH-DSA-256f on the federal path. Forgery requires breaking all three simultaneously.

Portability · The Attestation

Portable Attestation.

Q: What is a Portable Attestation in one sentence?

A signed JSON document carrying its own public keys, its own canonical payload, and three post-quantum signatures. It survives outside H33 and verifies outside H33.

Q: What survives if H33 disappears?

The attestation file is JSON, portable across email, SFTP, S3, blockchain anchor, archive tape, or hand-carried drive. The public keys ship inside it and the fingerprints are anchored in a witnessed offline ceremony, publishable independently of H33's continued existence.

A Portable Attestation is a post-quantum-signed document that binds three things together — a decision substrate, the verifier binary that confirms it, and the specific decisions being attested to. The result is an artifact a regulator, auditor, acquirer, or carrier can carry away, verify independently, and trust for the long term, without ever contacting H33. It is an expression of the H33-74 primitive, which produces and anchors the portable post-quantum evidence this document carries — it does not define a new primitive.

↑ Back to Portability

The 15-second test

"What is a Portable Attestation in one sentence?"

A signed JSON document carrying its own pubkeys, its own canonical payload, and three post-quantum signatures. It survives outside H33. It verifies outside H33. It is the load-bearing artifact of the Trustless Decision Attestation category.

How three artifacts agree without H33

The Portable Attestation is half of a four-artifact loop. The other half is the bundle the attestation refers to, plus the H33 Portability Verifier binary used to confirm them. The recipe is verbatim from the corpus:

"Bundle + Attestation + Portability Verifier all agree. No H33 contact required."

Bundle

The enterprise-portability .tar.gz carrying the canonical event log + manifest + SACRED state_id.

Attestation

A signed tda_v1 JSON pinning decisions + bundle hash + verifier hash.

Portability Verifier

The open-source binary that confirms the bundle replays to the pinned SACRED state_id.

The attestation verifier checks all three. Any tampering at any layer flips the verdict to FAIL — the PASS/FAIL determination itself is what Verification renders. The four-artifact loop is currently shipped, demonstrated, and verified end-to-end on a real fixture at /attestation/.

What survives if H33 disappears

The attestation file is JSON. It is portable across email, SFTP, S3, blockchain anchor, archive tape, or hand-carried drive. The public keys ship inside it. The fingerprints are anchored in a witnessed offline ceremony, publishable independently of H33's continued existence.

Three post-quantum families (ML-DSA-65 + FALCON-512 + SLH-DSA-128f on the commercial path; ML-DSA-87 + SLH-DSA-256f on the federal path) sign every attestation. Forgery requires breaking all three simultaneously. The attestation outlives the originating system by design.

The same portable form carries other kinds of evidence built on the same primitive: AI attestation, AI-decision attestation, and on-chain anchoring such as Arbitrum attestation.

Verify the loop end-to-end · no H33 contact required

Download the attestation issuer + verifier and run the four-artifact loop against a real enterprise bundle.

Get the Attestation Pair → All Five Surfaces →