Which EU AI Act obligations does H33-74 evidence support?

H33-74 produces evidence that maps to Article 12 automatic logging, Article 13 transparency to users, Article 14 human oversight, Article 17 quality management, and Article 61 post-market monitoring. Each control emits a receipt at the moment of execution.

Does the primitive change for the EU AI Act?

No. H33-74 is the same portable 74-byte post-quantum evidence primitive across every regulation. Only the crosswalk to the regulation differs; the primitive and its 74 bytes are unchanged.

Does producing H33-74 evidence make an organization fully compliant with the EU AI Act?

No. H33-74 produces verifiable evidence that supports EU AI Act requirements. Compliance is a determination made by the organization and its regulators; the evidence supports it but does not by itself satisfy the regulation.

How is an H33-74 receipt verified?

The audit team is given the receipt store and an open-source verifier and verifies each receipt independently and offline, without contacting H33 and without the operator's infrastructure being available.

Does the evidence survive system, vendor, and chain changes?

Yes. Each control's receipt outlives the system that produced it, the vendor that hosts it, and the chains it was anchored to. The post-quantum signatures survive the quantum transition and the chain anchors survive any single chain's deprecation.

H33-74 for the EU AI Act — Chain-Portable AI Evidence

H33-74 for EU AI Act

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 the EU AI Act. The primitive is unchanged; only the application context differs, and the evidence it produces supports (does not by itself satisfy) the regulation. EU AI Act (Regulation on Artificial Intelligence) requires verifiable evidence of operational controls. H33-74 produces that evidence as a chain-portable post-quantum receipt that survives the systems and chains it was anchored to.

EU AI Act (Regulation on Artificial Intelligence) (European Union, high-risk AI systems) places obligations on organizations to demonstrate that operational controls were in place, that AI and automated decisions were governed, and that an audit trail exists for regulatory inquiry. Most existing audit-log architectures meet the letter of the requirement but produce evidence that is tied to the operator's current systems. If those systems change or fail, the evidence weakens.

H33-74 produces audit evidence that survives the system that produced it. The receipt is cryptographically verifiable independent of the operator. The PQ signatures survive the quantum transition. The chain anchors survive any single chain's deprecation. The audit horizon is institutional, not application-bound.

What EU AI Act requires

The EU AI Act imposes obligations on providers and deployers of high-risk AI systems: risk management, data governance, technical documentation, record keeping, transparency, human oversight, accuracy and robustness. Article 12 specifically requires automatic logging of AI system activity to ensure traceability across the lifecycle. The logs must enable monitoring, post-market surveillance, and incident investigation by national competent authorities and the AI Office.

Why H33-74 fits

AI Act records have to survive the AI system's deployment lifecycle, vendor changes, and post-market surveillance horizons. Traditional logs leave the regulator dependent on the operator's word that the log is unaltered. H33-74 produces each AI decision as a cryptographically signed receipt that the regulator can verify directly. The receipt includes the model version, the input features (or their commitment), the output, the confidence, and the policy under which the decision was issued. Independent verification works regardless of the AI vendor's continued cooperation.

Control mapping

Article 12 logging

Each AI inference, decision, or autonomous action emits an H33-74 receipt at the moment of execution. Receipts include model identity, input commitment, output, and decision metadata.

Article 13 transparency to users

User-facing notifications, opt-outs, and consent records produce receipts that survive the platform that delivered them.

Article 14 human oversight

Human intervention events (override, escalation, correction) emit receipts that record who acted, when, and under what authority.

Article 17 quality management

Quality management decisions, model validation outcomes, and performance assessments produce receipts that compose into a verifiable QMS audit trail.

Article 61 post-market monitoring

Post-market monitoring events, incident classifications, and corrective actions emit receipts the AI Office can verify directly without operator coordination.

What this changes for the audit team

Each control's evidence is a cryptographic object the auditor verifies directly, not a log entry the auditor trusts because the operator says so.
The audit horizon extends beyond the operator's current systems, vendors, or chain choices.
Regulator inquiry years after a decision can be answered with the original PQ-signed receipt rather than reconstructed from operator memory.
Independent third-party verification works without the operator's infrastructure being available.

How H33-74 is integrated

For each control that produces a decision or outcome, the system emits an H33-74 receipt at the moment the decision is made.
Receipts are signed with three independent post-quantum signature families and contain the structured computation result.
Receipts are anchored on one or more chains as the audit policy requires (delayed or immediate, single-chain or multi-chain).
The audit team is given the receipt store and the open-source verifier. They verify independently.

The EU AI Act audit trail becomes chain-portable evidence. Each control's record outlives the system that produced it, the vendor that hosts it, and the chains it was anchored to.

H33-74 is the same primitive across every regulation — only the crosswalk differs. Compare the sibling mappings for GDPR and NIS2. Where the AI Act asks not just what a system decided but under whose authority, Agent-008 governs the AI decision and emits its authority package on this same H33-74 substrate.

The chain-portable evidence model

Read the architectural concept underneath every H33-74 regulatory deployment.

Chain Portability Why Chain Migration Shouldn't Exist