Post-Quantum Portable Attestation.
An independently verifiable artifact that survives the originating system.
The v0.1 Portability Verifier release proved a third party could independently reproduce a SACRED state_id from an enterprise bundle. This release closes the loop: the issuer produces a signed tda_v1 attestation (the canonical Trustless Decision Attestation category). The attestation verifier confirms the attestation, the bundle, and the Portability Verifier binary all agree. No H33 contact at any step. "Portable Object → Independent Verifier → Independent Reproduction. You have that for bundles. Now you have it for attestations." — Eric, June 4 2026
A Trustless Decision Attestation is a portable, post-quantum evidence artifact that H33-74 produces — a signed tda_v1 receipt binding a decision, its bundle, and the verifier version, so any third party can re-verify it offline against its schema and hashes, trusting no one.
Why this exists. Evidence that only its originating system can confirm is not evidence. The attestation exists so proof of what happened survives the system that produced it — reproducible by an outside party years later with no H33 contact.
What it is NOT. The attestation is the evidence, not the verdict. It does not render the independent verdict (that is Verification), it does not monitor operations (that is HATS), and it does not make the governance decision (that is Agent-008). H33-74 produces the artifact; Verification renders the verdict on it.
Q0 — Who bears risk? Never H33. This release bears attestation accuracy + issuance determinism + verifier correctness.
Q0.5 — Who owns the decision? Always the owner. The attestation verifier surfaces structural verdicts. It never judges decisions.
Determinism — Eric LOCKED: identical bundle + decision set + verifier version + signing key → byte-identical canonical payload (excluding issued_at_ms + signatures). Tested in the harness; passes.
v0.1.0 release
The three-artifact loop, end to end
A third party needs three downloads. Each comes from a different surface; together they prove agreement without H33.
tda_v1 JSONRun the loop
chmod +x h33-verify-attestation-v0.1.0-aarch64-apple-darwin
chmod +x h33-independent-canonical-replay-v0.1.0-aarch64-apple-darwin
./h33-verify-attestation-v0.1.0-aarch64-apple-darwin \
--attestation sample-attestation-claim-84711.tda_v1.json \
--bundle tenant_insurance_claim_44962d9b-25f5-5622-bd9a-98d5580bb8a2_enterprise_bundle.tar.gz \
--verifier-binary h33-independent-canonical-replay-v0.1.0-aarch64-apple-darwin- ✓ Issuer fingerprint internally consistent
- ✓ Canonical payload hash matches declared value
- ✓ All 3 PQ signatures verify (ML-DSA-65 · FALCON-512 · SLH-DSA-128f)
- ✓ Bundle hash anchor matches
- ✓ Portability Verifier binary hash anchor matches
- ✓ Each attested decision replays to its SACRED state_id
- → OVERALL: PASS ✓ — bundle + attestation + portability verifier all agree. No H33 contact required.
When to use an attestation — and when not to
- You need portable, offline-verifiable proof that a decision happened and survives infrastructure or the passage of time.
- An outside party (regulator, auditor, counterparty) must confirm the record without trusting — or contacting — H33.
- Evidence must remain re-verifiable for years, after keys rotate or the originating system is gone.
- You need the independent verdict rendered on the evidence — that is Verification. H33-74 hands it the artifact; Verification decides pass/fail.
- You need continuous operational monitoring or recording of a live control — that is HATS.
- You need the governance decision itself made or authority preserved — that is Agent-008.
Frequently asked questions
What exactly is this attestation?
It is the portable evidence artifact that H33-74 produces: a signed tda_v1 receipt that binds a decision, its bundle, and the verifier version into a self-contained record. Anyone holding it can re-check it offline against its schema and hashes. It is the proof-of-what-happened, not a claim you have to take on faith.
What does the attestation NOT do?
It does not render the independent verdict — that is Verification. It does not monitor or record live operations — that is HATS. It does not make the governance decision or preserve authority — that is Agent-008. H33-74 produces the evidence; the verdict on that evidence is a separate act by Verification.
How is this different from Verification?
H33-74 produces the attestation; Verification independently renders the verdict on it. The attestation verifier and Portability Verifier binaries confirm the artifact is internally consistent and reproduces its SACRED state; the final judgement of whether the evidence should be trusted is Verification's role, on a separate axis.
How is it independently verified?
Offline, by anyone, trusting no one. Download the open attestation verifier, the bundle, and the Portability Verifier binary, and run the six checks on an air-gapped machine. The SHA3-256 canonical payload hash and the three PQ signatures (ML-DSA-65, FALCON-512, SLH-DSA-128f — all external NIST-track standards H33 implements) are re-checked against the artifact. Any tampered byte makes the checks fail, so the result is tamper-evident, not something you take on trust.
Owner & boundaries
- H33-74 owns and produces this portable 74-byte post-quantum evidence primitive. This page is one of its Attestation & Receipts expressions.
- Verification independently renders the verdict on the evidence.
- HATS records and monitors operations continuously.
- Agent-008 governs the decision and preserves authority.
Honest v0.2 deferrals
- Multi-platform binaries (linux x86_64 · aarch64 · darwin x86_64)
- PQ-signed RELEASE artifacts (release signing key ceremony required)
- Byte-deterministic builds across machines (containerized toolchain)
- Production attestation-signing key ceremony (v0.1 uses dev keypair per
--signing-key-dir) - Attestation revocation registry
- Subscription / cadence infrastructure for periodic re-attestation
- CI/CD release automation