What does H33-74 attest for AI companies?

Model inferences and their governing policy, safety classifier decisions, RLHF reward model outputs, content moderation determinations, agent actions and tool calls, model lifecycle events, and user-facing safety interactions. Each emits an H33-74 proof at the moment it occurs.

Is the H33-74 primitive different for AI companies?

No. H33-74 is the same 74-byte post-quantum attestation primitive across every context — a 32-byte on-chain commitment plus a 42-byte compact receipt signed under three independent NIST post-quantum signature families. Only the application context differs for AI companies; the primitive is not redefined per vertical.

Which regulations does this evidence support?

H33-74 produces evidence that supports EU AI Act (Articles 12, 14, 17), GDPR (Articles 5, 22, 30), NIS2, and FedRAMP requirements. The evidence maps to these frameworks; it does not by itself make an organization fully compliant.

Can decisions still be verified after the model provider changes the model?

Yes. Every prior decision remains independently verifiable without the model provider's cooperation, because the proof is chain-portable and checked offline against the receipt bytes.

How is an H33-74 proof verified?

An independent, open verifier recomputes the 32-byte commitment from the receipt, checks the post-quantum signatures, and confirms the on-chain anchor — with no contact to H33.

H33-74 for AI Companies

Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.

This is H33-74 — the portable 74-byte post-quantum evidence primitive that produces and anchors operational proof — applied to AI companies. The primitive is unchanged; only the application context differs. Chief Trust Officers, VP Trust and Safety, Chief Compliance Officers, and Heads of Responsible AI at AI labs, AI infrastructure providers, and AI-product companies need operational evidence that survives infrastructure change, vendor turnover, and regulatory horizon shifts. H33-74 makes that evidence cryptographically verifiable and chain-portable by construction.

The asset may move. The evidence remains. Every approval, transfer, decision, and policy action your ai companies produces gets a 74-byte post-quantum-signed proof at the moment it happens. The proof outlives the system that produced it, the vendor that hosts it, and the chain it was anchored to.

What gets attested in ai companies

Each of the following operational events emits an H33-74 proof at the moment it occurs. The collection composes into the operational history that audit, compliance, and regulatory teams reconstruct from.

Model inferences and the policy under which each was issued.
Safety classifier decisions including thresholding rationale.
RLHF reward model outputs and preference judgments.
Content moderation determinations: allow, restrict, escalate, suspend.
Agent actions: tool calls, decisions taken on behalf of users, escalations.
Model lifecycle events: training run completion, evaluation outcome, deployment, deprecation.
User-facing safety interactions including refusals and disclaimers.

Regulatory pressure that already justifies this

AI Companies is regulated under frameworks whose audit horizons now extend past the lifetime of the systems and vendors holding the evidence. H33-74 produces evidence that survives that horizon:

EU AI Act. Article 12 logging plus Article 14 human oversight plus Article 17 quality management. See: EU AI Act crosswalk
GDPR. Articles 5, 22, 30 — automated decision-making and recordkeeping. See: GDPR crosswalk
NIS2. EU AI infrastructure providers. See: NIS2 crosswalk
FedRAMP. AI services in federal cloud environments. See: FedRAMP crosswalk
Voluntary commitments to the AI Safety Institute. US AI commitments under EO 14110 successors.

Scenarios this changes

Model provider changes the model underneath an application

Every prior decision the old model made remains independently verifiable. The application can answer regulator and customer questions about decisions made under the prior model without the model provider's cooperation.

Litigation requires evidence of safety classifier decisions

The proof of every classifier call, the threshold applied, the version of the classifier, and the disposition is produced. Verifiable without revealing model internals.

Audit of agent actions taken on behalf of an enterprise user

Each tool call, decision, escalation, and rationale is a separate proof. The enterprise verifies that the agent acted within authorized scope without trusting the AI vendor's log. Where the question is not just what happened but under whose authority, Agent-008 governs the agent and emits its authority package on this same H33-74 substrate. See also AI attestation and AI decision attestation for the general evidence patterns this vertical reuses.

What survives versus what gets replaced

Survives

Every approval, decision, transfer, compliance check, and policy action your operation produced — independently verifiable forever.

Gets replaced as normal lifecycle work

The core systems, the vendor SaaS contracts, the cloud, the database product, the chain you anchored to. Each replacement is engineering work, not an existential project.

AI Companies operational history compounds in value. Five years of approvals, decisions, and compliance determinations are usually worth more than the systems that produced them. H33-74 keeps that history independent of the infrastructure.

How to start

Three integration patterns, ordered by how invasive each is.

Pattern 1 — Receipt at the policy engine

The decision system (policy engine, approval workflow, AI scorer) emits an H33-74 proof for every decision at the moment it is made. No change to upstream systems. Auditors verify proofs directly.

Pattern 2 — Receipt at the system of record

Each system of record (treasury, claims, records, EHR) is wrapped so that committed transactions emit H33-74 proofs in addition to the existing audit log. Existing systems remain unchanged. Proofs become a parallel canonical record.

Pattern 3 — Receipt at the integration bus

Service mesh or integration bus intercepts cross-system events and emits H33-74 proofs. Highest reach, requires bus integration. Useful where systems-of-record cannot be modified.

See the architecture

The mechanism that makes ai companies evidence chain-portable.

Chain Portability What Gets Preserved