Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.
From the moment data is created to the moment it is verified — every step is sealed, structured, and cryptographically attested. No trust required.
Something happens.
Each capability is independently useful. Together they form the first system where truth at creation survives through computation, attestation, and verification — without ever requiring trust.
Data never exists as plaintext outside the hardware-attested generation boundary. Encrypted at creation. No plaintext emitted.
Compute role vs verify role, structurally separated. Possession of one key hierarchy does not confer access to the other.
Origin cryptographically bound at the moment of generation, before any processing, transmission, or storage occurs.
Typed claims with semantic class (Fact, Event, Control, State), subject scope, issuability profile. 202-byte fixed serialization.
Positively assert what was checked and found absent. Distinguishes "checked and not found" from "not checked." No other framework does this.
Append-only, PQ-attested. Claims interpreted against the schema in effect at issuance time. Prevents retroactive reinterpretation.
7 typed relations: References, Supersedes, Corrects, Retracts, DerivesFrom, Aggregates, ScopesToFragmentRoot. Original preserved in the verifiable record.
Merkle tree over artifact fragments with domain-separated leaf/node prefixes. Claims can target specific fragments of a document, not just the whole.
Compute SHA3-256 on encrypted data without decrypting. XOR = ciphertext addition (free). AND = programmable bootstrapping. Result threshold-decrypted. Data bits never exposed.
What was planned vs what actually happened, committed independently. Divergence between dispatch and execution is itself detectable and verifiable.
Customer-trained FHE classifier. Customers define taxonomy, train model on their data. H33 runs encrypted inference, emits policy tags. Three confidence modes: hard classification, threshold proof, customer-decrypted. Human override and feedback loop for retraining.
4-state machine: Valid, Invalid, Expired, Contested. Contested is a first-class terminal state, not forcibly resolved. Two conforming verifiers given identical inputs produce identical state.
Each node is an H33-74 commitment. Each edge references prior node's execution_root. Cross-party verification without accessing other parties' systems.
Amendment, Reversal, Disputed, SettledDispute. Disputed nodes suspend downstream processing. All corrections are themselves PQ-attested.
30+ year custody chains. Periodic on-chain balance verification. Discrepancies auto-generate DISPUTED claims. Fully reconstructable from blockchain + attestation primitives.
ZK-STARK proof (no trusted setup) proving: valid instrument, not previously redeemed, not disputed, past maturity, authorized holder. Reveals only instrument ID and redemption amount. Not holder identity.
Proof, not trust. Every capability produces independently verifiable output. No capability requires access to another party's internal systems. No capability requires trust in H33.
H33 does not use a general-purpose LLM to read customer documents. Customers define the taxonomy. H33 converts documents into encrypted feature vectors, evaluates a compact customer-specific classifier under FHE, and emits policy tags.
No score. No probability. A binary, attested tag. The system never sees the document.
TFHE proves the classification score exceeded the threshold. The score itself is never revealed.
The encrypted feature vector is returned to the customer. Only the customer's key can decrypt. H33 never holds the result.
Bond trade lifecycle — five parties, one chain of proof.
Creates trade record
SignedValidates trade
SealedClears trade
AttestedSettles trade
VerifiedZK proof of valid claim
ProvenFull chain proven. No trust required. Each party verifies its node and adjacent nodes without accessing the full workflow or any other party's internal systems.
What others do vs. what Upstream does.
H33 Products · Upstream Provenance
H33-Upstream is an upstream-provenance product. It proves that what upstream systems recorded actually happened — sealing data at creation and carrying an unbroken, independently checkable chain of proof from the first byte to the moment of verification. It owns the provenance-lifecycle workflow, the multi-party evidence experience, and the no-trust-required outcome. It does not own, redefine, or reimplement the encryption, proof, verification, or governance it relies on; it composes them.
The product boundary. H33-Upstream owns the upstream-provenance workflow and outcome. It uses H33 mechanisms for privacy, evidence, verification, and governance; it does not redefine or own those mechanisms.
Fully homomorphic encryption is what lets Upstream compute over sealed data without decrypting it, so provenance survives processing. Upstream consumes FHE; it does not define or implement it.
Verification is what lets any party independently confirm an attestation with no access to source data and no dependency on H33 — the pass/fail verdict. Upstream requests and surfaces that verdict; the verifying is owned elsewhere.
H33-74 supplies the portable 74-byte post-quantum attestation that carries provenance forward as portable evidence. Upstream attaches these attestations; it does not produce the attestation primitive.
Agent-008 governs any automated decisioning that acts on an Upstream attestation — preserving authority and preventing drift. Upstream is governed by it; it does not perform governance.
If Upstream swapped a signature family or its confidential-computing technology, it would still be H33-Upstream: the provenance-lifecycle workflow and no-trust outcome are the product. Mechanisms are chosen, not owned.
H33-Upstream is an upstream-provenance product. It proves that what upstream systems recorded actually happened, sealing data at creation and carrying an unbroken, independently checkable chain of proof to the moment of verification. It owns the provenance-lifecycle workflow and outcome; it uses H33 mechanisms for privacy, evidence, verification, and governance rather than reimplementing them.
It USES FHE to compute over sealed data without decrypting it, USES Verification so any party can confirm an attestation with no dependency on H33, USES H33-74 for the portable 74-byte post-quantum attestation, and is GOVERNED_BY Agent-008 for automated decisioning on attestations. It composes these; it does not own or redefine them.
Yes. Verification is fully independent: any party can check an attestation using the public verification protocol, with no dependency on H33 infrastructure and no access to source data. That independent verdict is owned by Verification, which Upstream uses.
Yes. If a signature family or the confidential-computing technology were replaced, it would still be H33-Upstream. The provenance-lifecycle workflow and no-trust outcome are what it owns. Mechanisms are chosen, not owned.
Use H33-Upstream when the problem is proving that upstream systems recorded what actually happened across a multi-party workflow, so downstream parties can trust the record without trusting the systems that produced it. The seal-at-creation, compute-without-decrypting, attestation, and independent-verification path are live; any figures shown are illustrative — verify current numbers on /benchmarks/.
When NOT to use it — use a neighbor instead. To prove the binaries and software supply chain running on your servers are clean, use Sentinel instead. To secure the API keys and secrets your services use, use H33-Gateway instead. To validate high-stakes documents (closings, claims, records), use H33-Vault instead.
If you want the mechanism, not the product. For the privacy mechanism itself, read FHE. For the proof/verdict layer, read Verification. For the portable attestation primitive, read H33-74.