PricingDemo
Log InGet API Key

HATS / EU AI Act Crosswalk

Document: H33-XWALK-EUAIA-001
Version: 1.0
Date: 2026-05-22
Framework: Regulation (EU) 2024/1689 (EU Artificial Intelligence Act)
Editor: Eric Beans, H33.ai, Inc.

1. Scope

This crosswalk maps HATS capabilities to the obligations imposed by the EU AI Act on providers and deployers of high-risk AI systems (Title III, Chapter 2). The EU AI Act entered into force on 1 August 2024 with a phased compliance timeline. Requirements for high-risk AI systems apply from 2 August 2026.

HATS capabilities address the technical documentation, record-keeping, transparency, human oversight, and post-market monitoring requirements. This crosswalk does not address prohibited AI practices (Title II), general-purpose AI model obligations (Title IIIA), or governance and enforcement provisions (Titles VI-XII).

This crosswalk is a technical mapping. It does not constitute a conformity assessment under Article 43 or replace the obligations of a notified body.

2. Risk Management (Article 9)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 9(1) Risk management system establishmentGovernance ReplayRisk management decision attestation receipts recording methodology and risk criteriaReplay risk management decisions to verify systematic approach was followed
Art. 9(2) Continuous iterative processContinuous Attestation + Evidence ChainsContinuous risk assessment attestation chain spanning the system lifecycleTraverse evidence chain to verify risk assessments occur at defined intervals throughout operation
Art. 9(5) Testing for risk managementEvidence ChainsTest execution attestation receipts linked to risk assessment findingsVerify test receipts exist for each identified risk; confirm predecessor hash linkage to risk assessments
Art. 9(8) Residual risk communicationIndependent VerificationResidual risk disclosure attestation receipts verifiable by deployersDeployers verify risk disclosure receipts using published public keys

3. Data and Data Governance (Article 10)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 10(2) Data governance and management practicesEvidence ChainsData governance event attestation chain recording data lineage decisionsTraverse data governance chain; verify each data handling decision was attested
Art. 10(3) Training data relevance and representativenessContinuous AttestationTraining data validation attestation receiptsVerify training data assessment receipts cover stated validation criteria
Art. 10(5) Personal data processing for bias detectionEncrypted ComputationFHE computation attestation receipts demonstrating bias detection on encrypted dataVerify computation_type indicates FHE operation; confirm data never exposed in plaintext during analysis

4. Technical Documentation (Article 11)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 11(1) Technical documentation drawn up before market placementEvidence ChainsDocumentation version attestation chain recording each documentation stateVerify attestation chain shows documentation existed before market placement timestamp
Art. 11(1) Kept up to dateContinuous AttestationPeriodic documentation state attestation receiptsVerify documentation attestation continuity; confirm updates attested within SLA

5. Record-Keeping (Article 12)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 12(1) Automatic recording of events (logs)Continuous AttestationPer-event attestation receipt stream with cryptographic bindingVerify receipt stream covers all system events; confirm no gaps in attestation coverage
Art. 12(2) Traceability of AI system functioningEvidence Chains + Agent AttestationTamper-evident evidence chain of all AI operations with per-action attestationTraverse evidence chain; verify each operation is individually attested with causal linkage
Art. 12(3) Logs retention for appropriate periodEvidence ChainsImmutable attestation receipt archive with cryptographic integrityVerify chain integrity from earliest receipt to current; confirm no receipts deleted or modified

6. Transparency (Article 13)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 13(1) Designed to allow interpretation of outputAgent Attestation + Governance ReplayPer-decision attestation receipts recording inputs, policy context, and outputsReplay agent decisions; verify input-output pairs are consistently attested
Art. 13(3)(b) Capabilities and limitationsIndependent VerificationCapability boundary attestation receipts verifiable by deployersDeployers verify capability attestation receipts independently
Art. 13(3)(d) Expected lifetime and maintenanceEvidence ChainsLifecycle attestation chain recording operational state over timeTraverse lifecycle chain to verify operational continuity and maintenance records

7. Human Oversight (Article 14)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 14(1) Designed for effective human oversightAgent AttestationHuman oversight event attestation receipts recording each human intervention pointVerify oversight receipts exist at defined intervention points; confirm human identity binding
Art. 14(4)(a) Understanding AI system capabilitiesGovernance ReplayCapability assessment attestation receipts with governance bindingReplay capability assessments; verify governance context includes human oversight acknowledgment
Art. 14(4)(b) Awareness of automation biasAgent Attestation + Evidence ChainsBias monitoring attestation chain with per-decision agent attestationTraverse bias monitoring chain; verify human review points are attested at defined intervals
Art. 14(4)(d) Ability to decide not to use or overrideGovernance ReplayOverride decision attestation receipts recording human override eventsReplay override decisions; verify human authority was exercised and attested
Art. 14(4)(e) Ability to intervene or interruptContinuous AttestationIntervention event attestation receipts with sub-second timestampsVerify intervention receipts demonstrate system responded to human interruption within SLA

8. Accuracy, Robustness, and Cybersecurity (Article 15)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 15(1) Appropriate level of accuracyContinuous AttestationAccuracy measurement attestation receipts at defined intervalsVerify accuracy measurement continuity; confirm measurements attested against stated thresholds
Art. 15(3) Resilience against errors, faults, inconsistenciesEvidence ChainsRobustness test attestation chain recording test results over timeTraverse test result chain; verify robustness testing coverage matches stated methodology
Art. 15(4) Cybersecurity measuresContinuous Attestation + Encrypted ComputationSecurity control attestation receipts; FHE computation receipts demonstrating data protectionVerify security control attestation continuity; confirm encrypted computation where required

9. Post-Market Monitoring (Article 72)

ArticleHATS CapabilityEvidence TypeVerification Method
Art. 72(1) Post-market monitoring systemContinuous AttestationPost-deployment attestation receipt stream covering all production operationsVerify attestation stream continuity from deployment date; confirm no monitoring gaps
Art. 72(3) Active and systematic data collectionEvidence ChainsSystematic data collection attestation chain with configurable samplingVerify data collection attestation coverage; confirm sampling methodology is attested
Art. 72(4) Analysis of collected dataGovernance Replay + Agent AttestationData analysis decision attestation receipts with governance bindingReplay analysis decisions; verify conclusions are bound to attested data collection events

10. Coverage Notes

HATS capabilities provide technical evidence relevant to Articles 9-15 and 72 of the EU AI Act. The following EU AI Act obligations are outside the scope of HATS technical capabilities and require separate organizational measures: conformity assessment procedures (Article 43), EU declaration of conformity (Article 47), CE marking (Article 48), registration obligations (Article 49), and serious incident reporting (Article 73).

For AI systems using HATS agent attestation, the per-action attestation receipts provide the granularity of record-keeping anticipated by the EU AI Act. Each agent tool invocation, LLM call, and output generation is individually attested with three post-quantum signatures, producing the "automatic recording of events" required by Article 12.