Portable Attestation.
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 forever, without ever contacting H33.
"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."
tda_v1 JSON pinning decisions + bundle hash + verifier hash.The attestation verifier checks all three. Any tampering at any layer flips the verdict to FAIL. 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.