AIGO — EU AI Act Annexes Mapping
1. Document Purpose
This document provides the AIGO mapping for the Annexes to Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744. The Annexes contain important classification, documentation, conformity, registration, and related regulatory information. They therefore form a critical part of the AIGO regulatory-mapping architecture. This document maps the Annex structure to:- AIGO AI-system classification;
- regulatory applicability;
- risk;
- controls;
- assessments;
- conformity;
- documentation;
- evidence;
- registration;
- assurance;
- monitoring;
- change management;
- governance; and
- lifecycle management.
2. Mapping Information
The Digital Omnibus amended Annex I, deleted one item from Section A, added Regulation (EU) 2023/1230 on machinery to Section B, modified Annex VIII, and added Annex XIV concerning the codes, categories, and corresponding AI-system types used for notification of conformity-assessment bodies.
3. Annex Governance Principle
AIGO should not treat the Annexes as a single classification list. Each Annex has a distinct legal function. The preferred model is:4. Annex Applicability Model
AIGO should determine the relevant Annex through a structured decision process:5. Annex I — Union Harmonisation Legislation
5.1 Legal Function
Annex I identifies Union harmonisation legislation relevant to the Article 6(1) high-risk pathway. The classification framework distinguishes AI systems that are safety components of products covered by the listed Union harmonisation legislation, or AI systems that are themselves such products, subject to the statutory conditions. The Commission’s draft high-risk guidance describes this as the first high-risk pathway.5.2 AIGO Mapping
AIGO Components:- AI System;
- Classification;
- Governance;
- Risk;
- Assessment;
- Conformity;
- Evidence;
- Assurance.
DIRECT / CONDITIONAL / CRITICAL
6. Annex I Classification Control
Control Name: Annex I Product-Related High-Risk Classification The control should determine:- applicable Union harmonisation legislation;
- product category;
- safety-component relationship;
- AI-system relationship;
- required conformity assessment;
- high-risk status;
- applicable transition;
- evidence.
7. Annex I Current Amendment
Regulation (EU) 2026/1744 amended Annex I. Among other changes, it:- deleted point 1 of Section A; and
- added Regulation (EU) 2023/1230 on machinery as point 21 of Section B.
8. Annex I Governance Record
For an Article 6(1) determination, AIGO should maintain:9. Annex I and Product Compliance
AIGO should maintain a relationship among:10. Annex I and Notified Bodies
Where third-party conformity assessment is required, Annex I classification may affect:- notified-body scope;
- assessment module;
- product law;
- AI Act assessment;
- certification.
11. Annex II — Governance Treatment
The AIGO mapping shall verify the current consolidated legal text before treating Annex II as an operational classification source. The Annex numbering in a version-controlled regulatory mapping must not be inferred from secondary summaries. Where an Annex has been repealed, renumbered, or otherwise altered by subsequent legislation, the registry should preserve its historical status. Recommended states include:12. Annex III — High-Risk AI Systems Referred to in Article 6(2)
12.1 Legal Function
Annex III defines specified high-risk AI use cases for the Article 6(2) pathway. The Commission’s current draft high-risk guidance identifies Annex III as the second principal high-risk classification pathway.12.2 AIGO Mapping
Relationship:DIRECT / CRITICAL
12.3 AIGO Requirement
The organization should record:- Annex III area;
- exact use case;
- intended purpose;
- actor;
- affected persons;
- applicable exception;
- high-risk determination;
- evidence;
- effective date.
13. Annex III Areas
The current Annex III structure covers high-risk use cases in areas including:- biometrics;
- critical infrastructure;
- education and vocational training;
- employment, workers management and access to self-employment;
- access to and enjoyment of essential private and public services and benefits;
- law enforcement;
- migration, asylum and border control;
- administration of justice and democratic processes.
14. Annex III Classification Control
Control Name: Annex III High-Risk Use-Case Classification The control should:- identify the relevant Annex III category;
- assess the precise use case;
- evaluate applicable Article 6 conditions;
- consider statutory exceptions;
- record classification rationale;
- retain evidence.
15. Annex III and Article 5
The organization must perform Article 5 screening before treating an Annex III system as merely high-risk. The governance sequence is:- prohibited;
- high-risk;
- neither;
- subject to other obligations.
16. Annex III and Fundamental Rights
Annex III systems may have significant effects on:- employment;
- education;
- access to services;
- law enforcement;
- migration;
- justice;
- democratic processes.
- Risk;
- Assessment;
- Fundamental Rights;
- Human Oversight;
- Monitoring;
- Evidence;
- Assurance.
17. Annex III and Article 27
Where Article 27 applies, the Annex III classification should feed the Fundamental-Rights Impact Assessment. Recommended chain:18. Annex III Review and Regulatory Change
The Commission conducts annual review of the prohibited-practice list and Annex III high-risk use cases under Article 112(1). Its 2026 review report considered whether the list remains appropriate as AI technology develops. AIGO should therefore treat Annex III as a controlled regulatory-change object.19. Annex IV — Technical Documentation
19.1 Legal Function
Annex IV defines the information that must be included in the technical documentation for applicable high-risk AI systems.19.2 AIGO Mapping
Relationship:DIRECT / CRITICAL
19.3 AIGO Controls
- Technical Documentation Control;
- Document Integrity Control;
- Change Management Control;
- Evidence Control;
- Assurance Control.
20. Annex IV Documentation Structure
The AIGO technical-documentation framework should account for the legal categories in Annex IV, including, as applicable:- general description;
- intended purpose;
- system architecture;
- development methods;
- design specifications;
- data requirements;
- computational resources;
- training;
- validation;
- testing;
- risk management;
- human oversight;
- performance;
- accuracy;
- robustness;
- cybersecurity;
- lifecycle;
- post-market monitoring.
21. Annex IV and AIGO AI System Profile
The AIGO AI System Profile can provide the operational foundation for many Annex IV data points. However:22. Annex IV and Evidence
Each material technical-documentation component should be traceable to:- source;
- version;
- owner;
- review;
- supporting evidence.
23. Annex IV and Change Management
Changes affecting:- architecture;
- model;
- training;
- data;
- intended purpose;
- performance;
- human oversight;
- cybersecurity;
- deployment
24. Annex IV and Document Integrity
The Document Integrity Checker should verify:- existence;
- readability;
- version;
- metadata;
- integrity;
- required references;
- internal consistency.
25. Annex V — EU Declaration of Conformity
25.1 Legal Function
Annex V establishes the information to be included in the EU declaration of conformity.25.2 AIGO Mapping
Relationship:DIRECT / CRITICAL
25.3 AIGO Control
EU Declaration of Conformity Governance Control The control should maintain:- declaration;
- applicable AI system;
- applicable legislation;
- provider;
- authorized signatory;
- date;
- version;
- supporting conformity evidence.
26. Annex V and AIGO Approval
An internal approval decision should remain separate from the EU declaration.27. Annex V and Change Management
When a system changes, AIGO should determine whether the declaration of conformity must be:- updated;
- replaced;
- reassessed;
- supplemented.
28. Annex VI — Conformity Assessment Based on Internal Control
28.1 Legal Function
Annex VI establishes the conformity-assessment procedure based on internal control for applicable high-risk AI systems.28.2 AIGO Mapping
Relationship:DIRECT / CONDITIONAL
28.3 AIGO Implementation
Where legally applicable, AIGO can support:- internal control;
- documentation;
- risk management;
- QMS;
- testing;
- monitoring;
- evidence;
- corrective actions;
- review.
29. Annex VI and Internal Assessment
AIGO should distinguish:30. Annex VII — Conformity Assessment Based on Quality Management System and Assessment of Technical Documentation
30.1 Legal Function
Annex VII provides the conformity-assessment procedure involving quality management and, as applicable, assessment of technical documentation.30.2 AIGO Mapping
Relationship:DIRECT / CRITICAL
AIGO should support:
- QMS evidence;
- technical documentation;
- notified-body interaction;
- assessment findings;
- corrective actions;
- certificate;
- surveillance.
31. Annex VII and Notified Bodies
Where a notified body is required, AIGO should maintain:- body identity;
- scope;
- notification status;
- contract;
- assessment;
- findings;
- certificate;
- surveillance.
32. Annex VIII — Information to Be Submitted for Registration
32.1 Legal Function
Annex VIII defines information used for registration-related purposes under the AI Act.32.2 AIGO Mapping
Relationship:DIRECT
32.3 AIGO Registration Control
The control should maintain:- registration applicability;
- required information;
- responsible person;
- submission;
- identifier;
- update;
- evidence.
33. Annex VIII Amendment
Regulation (EU) 2026/1744 deleted points 7 and 9 from Section B of Annex VIII. Therefore, AIGO registration templates and data structures must be checked against the current amended Annex VIII rather than relying on an older registration-information model.34. Registration Data Governance
Registration information should be sourced from authoritative AIGO records. Recommended chain:35. Registration and Change Management
Changes should trigger registration review where legally relevant. Potential triggers:- provider change;
- system identity change;
- intended-purpose change;
- classification change;
- conformity change;
- deployment change;
- other legally relevant metadata changes.
36. Annex IX — Information Relating to Registration
36.1 Legal Function
AIGO shall maintain the current legal function and content of Annex IX as specified in the consolidated Regulation. Where Annex IX contains registration-related information applicable to the organization’s role or system, the information should be represented in the AIGO registration and evidence model.36.2 AIGO Mapping
Relationship:DIRECT / CONDITIONAL
37. Annex IX and Registration Architecture
Where applicable:38. Annex X — Historical / Current-Status Verification
Where the consolidated AI Act contains Annex X material, the AIGO Registry shall record its current status explicitly. The registry should distinguish:- current Annex;
- amended Annex;
- superseded Annex;
- historical reference.
39. Annex XI — Historical / Current-Status Verification
As with Annex X, the current legal status and operational function of Annex XI must be verified against the consolidated Regulation. The AIGO mapping registry should maintain:- title;
- legal function;
- current status;
- applicable article;
- AIGO relationship;
- review date.
40. Annex XII — Historical / Current-Status Verification
AIGO shall record Annex XII using the current consolidated legal text. Where Annex XII supports:- registration;
- documentation;
- classification;
- notification;
- other administrative purposes;
41. Annex XIII — Historical / Current-Status Verification
AIGO shall verify the current legal function of Annex XIII from the consolidated Regulation. The mapping registry should identify:42. Annex XIV — Notified-Body Designation Scope
42.1 Current Legal Function
Regulation (EU) 2026/1744 added Annex XIV. Annex XIV provides the lists of codes, categories, and corresponding AI-system types used for the notification procedure under Article 30 and defines the scope of designation of conformity-assessment bodies notified under the AI Act.42.2 AIGO Mapping
Relationship:DIRECT / CONDITIONAL
43. Annex XIV — Why It Matters
Annex XIV provides a machine-oriented classification layer for conformity-assessment-body designation. The current Annex includes codes for:- AI systems subject to Annex I;
- specified Annex III biometric systems;
- symbolic AI and expert systems;
- machine learning excluding generative and GPAI systems;
- generative AI and GPAI-based systems;
- emerging AI technologies, including agentic AI.
44. Annex XIV Codes
The current Annex XIV identifies, among others:45. Annex XIV AIGO Control
Control Name: Conformity-Assessment-Body Scope Verification The control should verify:- applicable AI-system category;
- relevant Annex XIV code;
- notified body’s designated scope;
- requested assessment type;
- notification status;
- evidence of authority.
46. Annex XIV and Notified-Body Selection
The selection process should be:47. Annex XIV and Technology Categories
Annex XIV explicitly introduces technology-specific categories. AIGO should therefore preserve the distinction between:- legal risk category;
- technology category;
- conformity-assessment category;
- AIGO technical classification.
48. Annex XIV and Generative AI
The inclusion of generative AI and GPAI-based systems in Annex XIV means that AIGO should be prepared to map:49. Annex XIV and Agentic AI
Annex XIV includes emerging AI technologies not covered by other codes, including agentic AI. AIGO should therefore maintain the concept:AIH 0401 — Emerging AI technologies
as a technology-classification field where relevant.
This should not automatically be interpreted as a high-risk determination.
50. Annex XIV and AIGO Technical Classification
The AIGO AI System Profile may eventually include:51. Annex XIV and Supplier Governance
Where a notified body is procured, AIGO should require scope verification before engagement. Supplier evidence should include:- notification;
- scope;
- code;
- authority;
- validity;
- applicable assessment.
52. Annex XIV and Assurance
Assurance may review:- code selection;
- notified-body scope;
- current authorization;
- assessment scope;
- certificate relationship.
53. Annex XIV and Change Management
If the AI system changes technology category or intended use, AIGO should reassess:- Annex XIV code;
- conformity pathway;
- notified-body scope;
- assessment requirements.
54. Annex XIV and Registry
The AIGO Mapping Registry should eventually include Annex XIV codes as controlled values where operationally useful. Potential fields:55. Annex Crosswalk
The principal AIGO crosswalk is:
The table deliberately avoids inventing substantive requirements for Annexes whose current legal function needs direct verification from the consolidated Regulation.
56. Annex Lifecycle Mapping
57. Annex Risk Mapping
Potential AIGO risks include:58. Annex Control Matrix
59. Annex Evidence
AIGO evidence may include:- classification assessments;
- product-law evidence;
- intended-purpose documentation;
- technical documentation;
- test results;
- QMS records;
- conformity assessments;
- declarations;
- certificates;
- registration records;
- notified-body scope evidence;
- regulatory correspondence;
- change records;
- assurance reports.
60. Annex Traceability
The minimum Annex traceability chain is:61. Annex and Article Traceability
Annex mappings should always connect back to their governing Article. Examples:62. Annex and AIGO Schema Traceability
63. Annex and Control Coverage
The Control Coverage Validator should eventually identify:- applicable Annex;
- mapped AIGO control;
- implemented control;
- assessed control;
- evidenced control;
- assured control.
64. Annex and Evidence Coverage
The Evidence Coverage Validator should eventually identify:- missing technical documentation;
- missing classification evidence;
- missing registration evidence;
- missing conformity evidence;
- missing notified-body evidence.
65. Annex and Document Integrity
The Document Integrity Checker should verify:- mapping files;
- legal source references;
- Annex version;
- cross-reference integrity;
- registry consistency;
- controlled Annex references.
66. Annex and Framework Consistency
The Framework Consistency Checker should detect:- inconsistent Annex references;
- obsolete Annex names;
- incorrect article-to-annex relationships;
- stale dates;
- outdated product-law references;
- conflicting notified-body codes.
67. Annex and Repository Health
The Repository Health Checker should report:- Annex mapping completeness;
- legal-source currency;
- broken Annex references;
- inconsistent Annex numbering;
- unreviewed amendments;
- registration mapping gaps;
- conformity mapping gaps.
68. Digital Omnibus Impact
Regulation (EU) 2026/1744 materially affects the Annex architecture. At minimum, the AIGO mapping must account for:- Annex I changes;
- Annex VIII changes;
- new Annex XIV;
- revised Article 6 timeline;
- revised conformity framework;
- updated notified-body arrangements.
69. Annual Annex Review
The organization should monitor the AI Act’s annual review mechanism. The Commission’s 2026 report specifically evaluates whether the prohibited-practice list and Annex III high-risk use-case list need amendment. AIGO should therefore schedule:70. Annex Change Management
A change to an Annex should trigger:- source verification;
- affected requirement identification;
- affected AI-system identification;
- classification review;
- control-impact assessment;
- evidence-impact assessment;
- conformity-impact assessment;
- documentation impact;
- management review;
- implementation;
- verification.
71. Annex Applicability Findings
Potential findings include:72. Critical Annex Findings
Potential critical findings include:- high-risk classification relies on an obsolete Annex I or III version;
- required Annex IV documentation is materially absent;
- applicable conformity assessment has not been determined;
- required declaration is absent;
- registration requirements are not assessed;
- notified-body scope is not verified;
- Annex XIV code is incorrectly assigned for a required conformity assessment;
- material Annex amendment is not reflected in governance.
73. Annex Regulatory Currency
Each Annex mapping record should retain:- legal source;
- amendment;
- publication date;
- effective date;
- applicability date;
- source verification date;
- mapping version.
74. Annex Source Hierarchy
For Annex-specific questions, AIGO should use:75. Annex Review Frequency
Minimum:- annual;
- after every AI Act amendment;
- after new delegated acts;
- after implementing acts;
- after material Commission guidance;
- after major changes in harmonised standards or common specifications.
76. Annex Mapping Confidence
Each Annex mapping should support:77. Annex Governance Ownership
The Annex mapping package should have:- Mapping Owner;
- Legal/Compliance Reviewer;
- Conformity Reviewer;
- AI Governance Owner;
- Framework Architect;
- Evidence Owner;
- Assurance Reviewer.
78. Annex Registration and Machine Readability
A future AIGO mapping schema may include:79. Annex XIV Machine-Readable Extension
Because Annex XIV introduces standardized codes for AI-system categories and conformity-assessment-body designation, AIGO should consider adding:80. Annex and Third-Party Governance
Where third parties perform:- conformity assessment;
- notified-body functions;
- technical testing;
- verification;
- product compliance;
- authorization;
- scope;
- contract;
- deliverables;
- evidence;
- changes.
81. Annex and Management Review
Management review should consider:- material Annex changes;
- new high-risk categories;
- product-law changes;
- registration changes;
- conformity changes;
- notified-body changes;
- documentation gaps;
- regulatory timing.
82. Annex and Improvement
Annex-related gaps should feed AIGO Improvement. Examples:- outdated classification logic;
- stale product-law mappings;
- incomplete documentation;
- registration gaps;
- conformity-body scope gaps;
- new Annex XIV codes requiring system changes.
83. Annex and Retirement
When AI systems are retired, AIGO should preserve:- historical Annex classification;
- conformity records;
- technical documentation;
- declarations;
- certificates;
- registration;
- relevant regulatory communications.
84. Historical Annex Handling
AIGO should never rewrite a historical record solely to match a later Annex amendment. Instead:85. Annex Cross-Version Governance
A controlled record may state:86. Annex Evidence Pack
A high-risk AI evidence package may contain:87. Annex Control Matrix
88. Annex Traceability Example — Annex I
89. Annex Traceability Example — Annex III
90. Annex Traceability Example — Annex IV
91. Annex Traceability Example — Annex XIV
92. Annex Coverage
A future mapping validator should report:- legal completeness;
- AIGO implementation coverage;
- evidence coverage.
93. Annex Validation Requirements
The Annex mapping should satisfy:Source Validation
Each current Annex is identified from the consolidated legal text.Article Link Validation
Each Annex is linked to its governing Article where applicable.Classification Validation
Annex I and III are correctly connected to Article 6.Documentation Validation
Annex IV is connected to Article 11.Conformity Validation
Annexes V–VII are linked to the relevant conformity architecture.Registration Validation
Annexes VIII–IX are linked to registration requirements where applicable.Scope Validation
Annex XIV codes are linked to the relevant conformity-assessment-body scope.Amendment Validation
2026 amendments are reflected.Historical Validation
Historical Annex references remain distinguishable from current requirements.94. Limitations
This mapping cannot independently determine:- whether a particular product falls under Annex I;
- whether a particular use case falls within Annex III;
- whether an exception applies;
- whether technical documentation satisfies Annex IV;
- whether a conformity procedure is correctly selected;
- whether a notified body is legally eligible for a specific assessment;
- whether a declaration is legally valid;
- whether registration is required for a specific system.
95. Current Amendment Baseline
Regulation (EU) 2026/1744 is the principal current amendment incorporated into this mapping version. It:- modifies Annex I;
- modifies Annex VIII;
- adds Annex XIV;
- changes the high-risk application timetable;
- modifies conformity-assessment arrangements;
- changes certain supervisory and administrative structures.
96. Current Regulatory Review Baseline
The Commission’s May 2026 review of prohibited practices and Annex III demonstrates that the high-risk list is subject to ongoing regulatory review. AIGO should therefore monitor annual reviews and incorporate material amendments into:- classification;
- controls;
- assessments;
- evidence;
- conformity;
- monitoring.
97. Relationship to Other EU AI Act Mappings
98. Relationship to AIGO Schemas
99. Relationship to AIGO Tools
The Annex mapping should be supported by:- Schema Validator;
- Reference Validator;
- Traceability Validator;
- Control Coverage Validator;
- Evidence Coverage Validator;
- Framework Consistency Checker;
- Document Integrity Checker;
- Repository Health Checker.
100. Document Control
101. Document Status
Document: AIGO — EU AI Act Annexes Mapping Version: 0.1 Status: Draft Working Name: AIGO Full Name: AI Governance Operating Framework Document Identifier:AIGO-MAP-EUAI-010
Document Type: EU AI Act Mapping
This document maps the EU AI Act Annex architecture to the AIGO AI Governance Operating Framework, including product-related high-risk classification, Annex III use cases, technical documentation, declarations, conformity procedures, registration information, historical Annex management, and the new Annex XIV classification codes for conformity-assessment-body designation scope.
End of Document