What AI events does H33-74 attest?

Each of these emits a 74-byte proof at the moment of execution: model inference, safety classifier output, RLHF judgment, content moderation call, agent action, and model-lifecycle events such as training completion, evaluation, deployment, and deprecation.

Is H33-74 changed for AI decisions?

No. H33-74 is the same portable post-quantum evidence primitive here as everywhere else. Only the application context differs: the receipts record AI decision context such as prompt commitment, model version, sampling parameters, output commitment, and policy applied.

Which regulations does the evidence map to?

H33-74 produces evidence that maps to EU AI Act Article 12 (logging) and Article 14 (human oversight), GDPR Article 22 (automated decisions), and SOX 404 where AI is part of internal control over financial reporting. It produces supporting evidence; it does not by itself make an operator compliant.

H33-74 for AI Decisions

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

This is H33-74 evidence applied to AI decisions. Chief Trust Officers, Heads of Responsible AI, and Chief Compliance Officers need cryptographic evidence of every AI decision. H33-74 produces/anchors that evidence as a portable post-quantum proof at the moment each action occurs. The primitive is unchanged — only the application context (AI decisions) differs.

Every AI decision should be independently auditable years later, even if the model, the provider, and the wrapping application have all changed. H33-74 produces one cryptographically verifiable proof per ai decisions action. The collection of proofs is the operational history. The history survives the systems that produced it.

What gets attested in ai decisions

Each of the following AI events emits an H33-74 proof at the moment of execution:

Model inference: the prompt commitment, the model version, the temperature and sampling parameters, the output commitment, the policy applied.
Safety classifier output: the input commitment, the classifier version, the threshold applied, the classification result.
RLHF judgment: the comparison pair, the rater identity, the preference, the rationale.
Content moderation call: the content commitment, the policy in effect, the disposition (allow, restrict, escalate).
Agent action: the tool invoked, the parameters committed, the user authorization, the result.
Model lifecycle: training run completion, evaluation outcomes, deployment, deprecation, all as separate proofs.

Workflow

1. Decision produced

The AI system makes a decision (inference, classification, moderation call, agent action). The decision context — input, model version, policy, output — is hashed to a 32-byte commitment.

2. Receipt emitted

The H33-74 substrate produces a 74-byte receipt signed under three post-quantum families. The receipt records the computation type, the commitment, and the timestamp.

3. Anchor scheduled

The receipt enters the anchor queue. Batched anchoring posts a Merkle root over many receipts to the chain or chains the operator anchors on.

4. Verification on demand

An auditor verifying any AI decision later requests the receipt and the Merkle proof. The verifier confirms the three PQ signatures and the anchor commitment. No AI vendor cooperation required.

Regulatory anchoring

This use case lives under specific regulatory frameworks. H33-74 produces evidence that maps to each:

EU AI Act Article 12. Automatic logging of AI system activity. Each H33-74 receipt is one logging entry. See the crosswalk.
EU AI Act Article 14. Human oversight events emit receipts. Override decisions produce verifiable evidence.
GDPR Article 22. Automated decisions producing legal or significant effects emit receipts including the decision logic available to the data subject. See the crosswalk.
SOX 404. If AI is part of ICFR, each AI decision is part of the audit trail. See the crosswalk.

What survives infrastructure change

Survives

Every ai decisions action your operation produced — independently verifiable forever.

Gets replaced as lifecycle work

The systems, the vendor SaaS contracts, the chains you anchored to.

The ai decisions evidence is chain-portable. When the underlying systems change, the ai decisions record carries forward as PQ-signed proofs anchored to whichever chain is appropriate at the time.

None of this redefines the primitive: H33-74 produces/anchors the same portable 74-byte post-quantum receipt for an AI decision that it does for any other event. When those decisions are made under governed authority, that authority is owned by Agent-008; how anyone independently checks a receipt is described under Verification.

See the architecture

Chain portability is the mechanism that makes ai decisions evidence infrastructure-independent.

Chain Portability What Gets Preserved