AIGO — EU AI Act Applicability and Timeline

1. Document Purpose

This document defines the controlled applicability and timeline model for the AIGO mapping of Regulation (EU) 2024/1689, the EU Artificial Intelligence Act, as amended by Regulation (EU) 2026/1744. Its purpose is to establish a single authoritative timeline for:

entry into force;
phased application;
prohibited AI practices;
AI literacy;
governance;
general-purpose AI;
transparency;
high-risk AI;
conformity assessment;
registration;
enforcement;
transitional provisions;
significant-change rules;
public-authority transition requirements; and
future regulatory review.

This document is the authoritative timeline source for the other EU AI Act mapping files in: mappings/eu-ai-act/ Those files should reference this document instead of independently maintaining competing application dates. This document is an operational regulatory mapping and does not constitute legal advice or a legal determination of applicability for a specific organization.

2. Mapping Information

Field	Value
Mapping	AIGO EU AI Act Applicability and Timeline
Version	0.1
Status	Draft
Document Identifier	`AIGO-MAP-EUAI-011`
Document Type	EU AI Act Mapping
Mapping Package	`AIGO-MAP-EUAI`
Primary Legal Instrument	Regulation (EU) 2024/1689
Current Amendment	Regulation (EU) 2026/1744
Primary Timeline Provision	Article 113
Transitional Provision	Article 111
Mapping Architecture	`AIGO-MAP-EUAI-ARCH-001`
Registry	`00-AIGO-EU-AI-Act-Mapping-Registry-v0.1.json`
Current Baseline Date	14 August 2026

Regulation (EU) 2026/1744 was signed on 8 July 2026, published in the Official Journal on 24 July 2026, and entered into force on 27 July 2026. It amended the AI Act’s application timetable and transitional arrangements.

3. Authoritative Timeline Principle

The AIGO EU AI Act mapping package shall maintain one controlled timeline source. The authoritative sequence is:

Legal Source
      ↓
Applicability Rule
      ↓
Effective / Application Date
      ↓
Transitional Rule
      ↓
Affected AI System
      ↓
Actor
      ↓
AIGO Requirement
      ↓
Control / Assessment / Evidence

The organization must distinguish:

legal entry into force;
entry into application;
enforcement availability;
transitional deadlines;
future compliance deadlines;
voluntary early-readiness dates.

These concepts are not interchangeable.

4. Entry Into Force of the AI Act

Regulation (EU) 2024/1689 entered into force on: 1 August 2024. The original AI Act established a staggered implementation model rather than making all provisions applicable immediately. Regulation (EU) 2026/1744 subsequently revised parts of that timetable. AIGO should therefore maintain:

Entry Into Force:
1 August 2024

separately from the application dates below.

5. Digital Omnibus Entry Into Force

Regulation (EU) 2026/1744 entered into force on: 27 July 2026. This date is legally significant because several provisions of the amended AI Act began applying on that date, including Articles 102–110 as specified by the amended Article 113. AIGO should maintain:

Digital Omnibus:
Signed: 8 July 2026
Published: 24 July 2026
Entered into force: 27 July 2026

6. Master Timeline

The current AIGO baseline is:

Date	Requirement / Event	Status
1 Aug 2024	AI Act entered into force	Historical / foundational
27 Jul 2026	Regulation (EU) 2026/1744 entered into force	Current
2 Feb 2025	Chapters I and II generally apply	Current
2 Feb 2025	Most original Article 5 prohibitions and AI-literacy provisions apply	Current
2 Aug 2025	Governance rules and GPAI obligations apply	Current
2 Aug 2026	General AI Act application date	Current
2 Aug 2026	Article 50 transparency framework generally applies	Current
2 Dec 2026	Newly amended Article 5 provisions apply	Future
2 Dec 2026	Certain pre-existing synthetic-content systems must comply with Article 50(2)	Future
2 Dec 2027	Chapter III Sections 1–3 apply to Article 6(2) / Annex III high-risk systems	Future
2 Aug 2028	Chapter III Sections 1–3 apply to Article 6(1) / Annex I high-risk systems	Future
2 Aug 2030	Public-authority high-risk systems must comply under Article 111(2)	Future

The 2026 amendment explicitly establishes the revised 2026, 2027, and 2028 dates and the 2030 public-authority deadline.

7. 1 August 2024 — Entry Into Force

The AI Act entered into force on: 1 August 2024. Entry into force means the Regulation became part of the EU legal order; it does not mean that every substantive obligation became applicable on that date. AIGO should therefore never describe 1 August 2024 as the universal compliance deadline.

8. 2 February 2025 — Chapters I and II

Under the amended Article 113, Chapters I and II apply from: 2 February 2025 except for the newly introduced or amended Article 5 provisions specified separately for application from 2 December 2026. The Commission summarizes the earlier application date as covering:

definitions;
prohibited AI practices under the initial prohibition set;
AI literacy;
other provisions within the applicable Chapters I and II.

9. AI Literacy — 2 February 2025

AI literacy obligations began applying on: 2 February 2025. The amended Article 4 retains the requirement for providers and deployers to take measures to support AI literacy while clarifying that they are not required to guarantee a specific level of AI literacy for an individual. AIGO status:

CURRENTLY_APPLICABLE

Detailed mapping: 06-AIGO-EU-AI-Act-AI-Literacy-Mapping-v0.1.md

10. Original Article 5 Prohibitions — 2 February 2025

The original Article 5 prohibition framework became applicable from: 2 February 2025 subject to the specific later application date for the provisions added or revised by the 2026 amendment. AIGO should therefore not use one single “Article 5 effective date” field. Instead:

Article 5 Provision
+
Specific Point / Paragraph
+
Application Date

should be stored.

11. New Article 5 Provisions — 2 December 2026

The 2026 amendment provides that specified new or amended Article 5 provisions apply from: 2 December 2026. AIGO should classify these as:

FUTURE_APPLICABLE

until that date. The Article 5 mapping must identify the specific provision rather than treating all prohibited practices as sharing an identical application date.

12. 2 August 2025 — Governance Rules

The Commission identifies: 2 August 2025 as the application date for the governance rules. This includes the AI governance architecture established by the AI Act. AIGO governance mappings should therefore treat the relevant governance requirements as:

CURRENTLY_APPLICABLE

13. 2 August 2025 — GPAI Obligations

The GPAI obligations became applicable on: 2 August 2025. The Commission confirms this date in its current GPAI implementation guidance. AIGO status:

CURRENTLY_APPLICABLE

Detailed mapping: 05-AIGO-EU-AI-Act-GPAI-Mapping-v0.1.md

14. 2 August 2026 — General Application Date

The general application date is: 2 August 2026. The Commission continues to describe 2 August 2026 as the AI Act’s general application date, subject to the specific exceptions and later dates established by the amended Article 113. As of this mapping version’s baseline date: 14 August 2026 the general application date has already passed. AIGO should therefore treat the applicable provisions that have reached their legal application dates as operational rather than future readiness items.

15. Article 50 Transparency — 2 August 2026

Article 50 transparency obligations form part of the current AI Act implementation framework. The European Commission’s final transparency guidance confirms that Article 50 transparency obligations apply from: 2 August 2026. This includes the applicable obligations concerning:

direct interaction;
synthetic content;
deepfakes;
public-interest AI-generated text;
emotion recognition;
biometric categorisation.

Detailed mapping: 04-AIGO-EU-AI-Act-Transparency-Mapping-v0.1.md

16. 2 December 2026 — Pre-Existing Synthetic Content

Article 111(4), as added by Regulation (EU) 2026/1744, provides a specific transition for providers of AI systems, including general-purpose AI systems, generating synthetic audio, image, video, or text content that were placed on the market before: 2 August 2026. Those providers must take the necessary steps to comply with Article 50(2) by: 2 December 2026. AIGO should represent this as:

TRANSITIONAL

rather than:

17. 2 December 2027 — Annex III High-Risk AI

The revised Article 113 establishes: 2 December 2027 as the application date for Chapter III, Sections 1–3, for AI systems classified as high-risk under:

Article 6(2); and
Annex III.

This includes the main requirements concerning:

risk management;
data and data governance;
technical documentation;
record keeping;
transparency;
human oversight;
accuracy;
robustness;
cybersecurity;
provider/deployer obligations;
conformity-related governance.

The legal text expressly sets this date.

18. 2 August 2028 — Annex I High-Risk AI

The revised Article 113 establishes: 2 August 2028 as the application date for Chapter III, Sections 1–3, for AI systems classified as high-risk under:

Article 6(1); and
Annex I.

This creates a separate timetable for high-risk AI embedded in regulated products. The Commission’s current implementation material confirms the same distinction.

19. High-Risk Timeline Architecture

AIGO must maintain two separate high-risk application fields:

HIGH_RISK_ANNEX_III_APPLICATION_DATE
=
2 December 2027

HIGH_RISK_ANNEX_I_APPLICATION_DATE
=
2 August 2028

This must not be collapsed into one generic “high-risk effective date.”

20. Public-Authority High-Risk Systems — 2 August 2030

Article 111(2), as amended by Regulation (EU) 2026/1744, provides that providers and deployers of high-risk AI systems intended to be used by public authorities must take the necessary steps to comply with the Regulation by: 2 August 2030. This is an additional transitional rule. AIGO should represent it as:

PUBLIC_AUTHORITY_TRANSITION

It should not override the ordinary application-date fields for other systems.

21. High-Risk Systems Placed on the Market Before Chapter III Application

Article 111(2), as amended, states that for other high-risk AI systems placed on the market or put into service before the relevant Chapter III application date, the Regulation applies only if those systems undergo significant changes in design from that date, subject to the separate public-authority rule. AIGO should therefore record:

SYSTEM_MARKET_STATUS
+
ORIGINAL_DATE
+
SIGNIFICANT_CHANGE
+
CHAPTER_III_APPLICATION_DATE

22. Significant-Change Trigger

For transitional high-risk systems, a significant design change may cause the relevant high-risk obligations to apply. AIGO should therefore include a: High-Risk Significant-Change Assessment with:

original system version;
original market date;
change date;
change description;
design impact;
legal assessment;
conformity impact;
documentation impact;
decision.

23. Significant Change and AIGO Change Management

The relationship should be:

Change Request
      ↓
Significant-Change Assessment
      ↓
Does Article 111(2) Trigger Application?
      ↓
Yes / No
      ↓
Conformity / Controls / Documentation

This assessment should be integrated with: 11-AIGO-AI-Change-Management-Template-v0.1.md and the corresponding Change Schema.

24. 27 July 2026 — Articles 102–110

Regulation (EU) 2026/1744 adds a specific Article 113 date stating that Articles 102–110 apply from: 27 July 2026. These provisions should therefore be treated as currently applicable from the Digital Omnibus entry-into-force date. AIGO should not use 2 August 2026 as a universal date for all amended provisions.

25. Timeline Categories

AIGO should use controlled applicability values:

NOT_YET_IN_FORCE
IN_FORCE_NOT_YET_APPLICABLE
CURRENTLY_APPLICABLE
TRANSITIONAL
FUTURE_APPLICABLE
HISTORICAL
SUPERSEDED
NOT_APPLICABLE

These values allow legal status and operational readiness to be represented separately.

26. Entry Into Force Versus Application

AIGO shall distinguish:

Entry Into Force

The legislation becomes legally operative as a Union legal instrument.

Entry Into Application

A specific provision begins imposing or activating its substantive requirements.

Enforcement Availability

A competent authority obtains the applicable power or responsibility to supervise/enforce.

Transitional Deadline

An additional date by which a covered existing system must complete compliance steps. These are separate data concepts.

27. Regulatory Timeline Record

Each timeline record should include:

Field	Purpose
Event ID	Stable identifier
Legal Instrument	Source
Article / Annex	Provision
Paragraph / Point	Precision
Event Type	Entry into force / application / transition
Date	Effective date
Actor	Affected role
AI Category	Affected system
Condition	Applicability condition
Status	Current / historical / future
Source	Legal source
Review Date	Currency

28. Recommended Timeline IDs

The current package should use stable identifiers such as:

EUAI-TIME-001
EUAI-TIME-002
EUAI-TIME-003
...

The exact number should be maintained in the mapping registry.

29. Core Timeline Records

Recommended initial records:

EUAI-TIME-001
AI Act Entry Into Force
2024-08-01

EUAI-TIME-002
Chapters I and II
2025-02-02

EUAI-TIME-003
Governance
2025-08-02

EUAI-TIME-004
GPAI
2025-08-02

EUAI-TIME-005
General Application
2026-08-02

EUAI-TIME-006
Article 50 General Application
2026-08-02

EUAI-TIME-007
New Article 5 Provisions
2026-12-02

EUAI-TIME-008
Article 50(2) Transitional Deadline
2026-12-02

EUAI-TIME-009
Annex III High-Risk
2027-12-02

EUAI-TIME-010
Annex I High-Risk
2028-08-02

EUAI-TIME-011
Public Authority High-Risk Transition
2030-08-02

EUAI-TIME-012
Articles 102–110
2026-07-27

30. Application Status as of 14 August 2026

At this document’s baseline date:

Currently Applicable

AI Act is in force;
Chapters I and II applicable, subject to specified exceptions;
AI literacy;
original applicable prohibitions;
governance;
GPAI obligations;
general AI Act provisions reaching their application dates;
Article 50 transparency obligations;
Articles 102–110 under the amended schedule.

Future

new Article 5 provisions: 2 December 2026;
pre-existing synthetic-content Article 50(2) transition deadline: 2 December 2026;
Annex III high-risk Chapter III Sections 1–3: 2 December 2027;
Annex I high-risk Chapter III Sections 1–3: 2 August 2028;
public-authority high-risk transition: 2 August 2030.

This classification is based on the current amended Article 113 and Article 111.

31. AIGO Current-State Rule

At any point in time, the applicability engine should calculate:

Applicable Today

from:

event date;
current date;
actor;
AI category;
transition;
legal condition.

It should not simply compare the current date with one global AI Act deadline.

32. Applicability Decision Algorithm

A conceptual decision sequence is:

1. Identify legal provision
        ↓
2. Identify source version
        ↓
3. Check entry into force
        ↓
4. Check application date
        ↓
5. Check actor
        ↓
6. Check AI-system category
        ↓
7. Check geographic / role conditions
        ↓
8. Check exemptions
        ↓
9. Check transitional provisions
        ↓
10. Check significant-change rules
        ↓
11. Determine current status

33. Applicability Status Examples

Example A — Article 4 AI Literacy

Provision:
Article 4

Application:
2 February 2025

Current Date:
14 August 2026

Status:
CURRENTLY_APPLICABLE

Example B — Annex III High-Risk Obligation

Provision:
Chapter III Sections 1–3

Category:
Article 6(2) / Annex III

Application:
2 December 2027

Current Date:
14 August 2026

Status:
FUTURE_APPLICABLE

Example C — Annex I High-Risk Obligation

Provision:
Chapter III Sections 1–3

Category:
Article 6(1) / Annex I

Application:
2 August 2028

Status:
FUTURE_APPLICABLE

34. Early-Readiness Status

AIGO should separately support:

LEGAL_STATUS = FUTURE_APPLICABLE
AIGO_READINESS = IMPLEMENTED_EARLY

This allows organizations to prepare before the statutory date without incorrectly claiming that the requirement is currently legally applicable.

35. Early Implementation Rule

Where an organization voluntarily implements a future requirement early, the evidence should identify:

legal application date;
organizational implementation date;
reason for early implementation;
implemented scope;
whether the organization intends to maintain the control until legal application.

36. Mapping Document Rule

All EU AI Act mapping documents should refer to this timeline document for dates. For example:

See:
11-AIGO-EU-AI-Act-Applicability-and-Timeline-v0.1.md

A detailed document may mention a date for readability, but the authoritative date should remain centralized here.

37. No Duplicate Timeline Authority

The following files should not independently become competing timeline sources:

main mapping;
prohibited practices mapping;
high-risk mapping;
transparency mapping;
GPAI mapping;
AI-literacy mapping;
governance mapping;
conformity mapping;
rights mapping;
Annex mapping.

Those documents may describe relevant dates but should reference this document as authoritative.

38. Timeline Change Control

Any change to an application date should require:

legal source verification;
impact analysis;
timeline update;
affected mapping identification;
consistency validation;
evidence update;
review;
approval.

39. Regulatory Change Example

If the EU changes the Annex III application date:

Legal Amendment
     ↓
Timeline Record Updated
     ↓
High-Risk Mapping Updated
     ↓
Conformity Mapping Updated
     ↓
Control Mapping Updated
     ↓
Evidence Mapping Updated
     ↓
Repository Consistency Check

40. Timeline and Control Activation

AIGO controls may be:

NOT_REQUIRED_YET
PLANNED
EARLY_IMPLEMENTATION
CURRENTLY_REQUIRED
TRANSITIONAL
RETIRED

This is an AIGO operational status and should not be confused with the legal status.

41. Timeline and Assessment Activation

Assessments should use the legal timeline to determine whether they are:

required now;
required in transition;
required before a planned deployment;
future readiness;
not applicable.

42. Timeline and Approval

An approval workflow should verify:

current legal status;
future obligations;
transition;
planned implementation date;
relevant controls.

A future legal requirement may become an approval condition before its legal application date as an organizational risk decision.

43. Timeline and Monitoring

Monitoring should track approaching deadlines. Recommended indicators:

Days to Application
Days to Transition Deadline
Days to Public-Authority Deadline
Open Readiness Gaps
Open Regulatory Changes

These are management indicators, not statutory compliance metrics.

44. Timeline and Incident Management

A missed application deadline or transition deadline may become a regulatory incident. AIGO should record:

provision;
deadline;
affected system;
missed action;
cause;
containment;
remediation;
authority notification if applicable.

45. Timeline and Change Management

The Change Management process should evaluate whether legal timing creates:

immediate implementation;
future implementation;
transition;
grandfathering;
significant-change trigger.

46. Timeline and Management Review

Management review should include upcoming material dates. Recommended horizon:

90 days;
180 days;
12 months;
next major regulatory milestone.

The organization may use different horizons according to risk.

47. Timeline and Assurance

Assurance should periodically verify that:

legal dates are current;
controls activated on time;
transition provisions are correctly applied;
early-readiness claims are labelled;
significant-change triggers are assessed.

48. Timeline Evidence

Evidence should include:

legal source;
amendment;
applicability assessment;
system classification;
transition assessment;
control activation;
readiness decision;
review.

49. Transition Evidence

For systems benefiting from a transition, AIGO should retain evidence of:

why transition applies;
relevant market date;
system version;
legal basis;
transition deadline;
actions taken;
final compliance date.

50. Grandfathering and Existing Systems

AIGO should avoid using the term “grandfathered” as a generic legal status. Instead, the system should record the precise transitional rule. For example:

Pre-existing system
+
Article 111(2)
+
No significant design change
=
Specific transitional treatment

The legal outcome depends on the exact provision.

51. Pre-Existing High-Risk Systems

For non-public-authority high-risk systems placed on the market or put into service before the relevant Chapter III application date, Article 111(2) provides a significant-change trigger for the later application of the Regulation. AIGO should therefore maintain historical market-placement information.

52. Public-Authority Systems

For high-risk AI systems intended to be used by public authorities, the amended Article 111(2) requires necessary compliance steps by: 2 August 2030. AIGO should maintain a distinct public-authority applicability flag.

53. Public-Authority Flag

Recommended controlled value:

PUBLIC_AUTHORITY_USE

Possible values:

YES
NO
UNCERTAIN

This field should influence the applicability engine.

54. Timeline and Annex XIV

Annex XIV is part of the current amended legal architecture. Its notified-body designation scope should be evaluated according to the current legal regime, including the transitional arrangements concerning certain notified bodies. This is especially important for Article 6(1) systems subject to the later 2028 application date.

55. Timeline and GPAI

GPAI obligations became applicable on: 2 August 2025 and remain currently applicable. AIGO should distinguish:

GPAI obligation application

from:

High-risk application for downstream AI systems

A downstream system may have a different regulatory timeline.

56. Timeline and Transparency

Article 50 is now in the general application period, but Article 111(4) creates a specific transition for certain pre-existing synthetic-content systems until: 2 December 2026. AIGO should therefore calculate Article 50 applicability at system level rather than using a simple organization-wide date.

57. Timeline and Prohibited AI

The 2026 amendment introduced later application dates for specified Article 5 provisions. AIGO should therefore map each prohibited-practice record to:

article;
paragraph;
point;
effective date;
transitional status.

58. Timeline and AI Literacy

AI literacy remains a current obligation. The organization should not postpone Article 4 governance until the later high-risk dates.

59. Timeline and Governance

Governance obligations are already applicable. The AIGO Governance model should therefore be considered a current implementation area rather than a future-only framework.

60. Timeline and Enforcement

The amended AI Act also sets application dates for specific supervisory and enforcement provisions. Articles 102–110 apply from: 27 July 2026. AIGO should therefore update its governance/enforcement readiness baseline accordingly.

61. Timeline and Regulatory Authorities

Because supervisory competence can differ by AI system and actor, applicability records should include:

authority;
jurisdiction;
legal provision;
application date;
enforcement date where distinct.

The organization should not assume that every obligation is enforced by the same EU or national body.

62. Regulatory Date Source Control

Every timeline event should include a source reference. Recommended source types:

EUR_LEX_PRIMARY
EU_OFFICIAL_JOURNAL
EUROPEAN_COMMISSION
EU_AI_OFFICE
OTHER_OFFICIAL

Secondary sources should not become the authoritative source.

63. Timeline Source Currency

The timeline should be revalidated:

after every amendment;
after new implementing legislation;
after delegated acts;
after official implementation changes;
before each AIGO mapping release.

64. Current Legal Sources

The baseline source set for this version is:

Regulation (EU) 2024/1689

The foundational AI Act.

Regulation (EU) 2026/1744

The current Digital Omnibus amendment.

European Commission AI Act Regulatory Framework

The Commission’s current implementation timeline and AI Act overview.

European Commission AI Act FAQ

Current implementation and application explanations.

65. Timeline Registry

The machine-readable mapping registry should eventually include:

{
  "eventId": "EUAI-TIME-009",
  "eventType": "APPLICATION",
  "date": "2027-12-02",
  "scope": "HIGH_RISK_ANNEX_III",
  "legalSource": "Regulation (EU) 2026/1744",
  "status": "FUTURE_APPLICABLE"
}

The actual registry schema should remain aligned with: 00-AIGO-EU-AI-Act-Mapping-Registry-v0.1.json

66. Timeline Validation

The AIGO validation process should verify:

Date Accuracy

The date matches the current legal source.

Scope Accuracy

The date applies to the correct provision.

Actor Accuracy

Affected actors are identified.

System Accuracy

Affected AI categories are identified.

Transition Accuracy

Transitional rules are represented.

Change Accuracy

Significant-change rules are represented.

Status Accuracy

Current / future / transitional status is correct.

67. Timeline Findings

Potential findings include:

TIMELINE_SOURCE_MISSING
TIMELINE_DATE_CONFLICT
TIMELINE_SCOPE_CONFLICT
TIMELINE_ACTOR_CONFLICT
TIMELINE_TRANSITION_MISSING
TIMELINE_SIGNIFICANT_CHANGE_RULE_MISSING
TIMELINE_PUBLIC_AUTHORITY_RULE_MISSING
TIMELINE_STALE
TIMELINE_DUPLICATE_AUTHORITY
TIMELINE_STATUS_INCORRECT

68. Critical Timeline Findings

Potential critical findings include:

incorrect statutory application date;
high-risk timeline incorrectly centralized to one date;
transition deadline omitted;
public-authority transition omitted;
new Article 5 effective date omitted;
enforcement application date misrepresented;
obsolete 2024 timeline used without 2026 amendment.

69. Timeline and AIGO Repository Health

Repository Health should flag:

conflicting dates;
stale mapping files;
missing timeline registry;
duplicate timeline authorities;
unsupported future dates;
historical dates presented as current.

70. Timeline and Framework Consistency

The Framework Consistency Checker should compare:

this timeline document;
main mapping;
high-risk mapping;
transparency mapping;
GPAI mapping;
governance mapping;
conformity mapping;
Annex mapping;
machine-readable registry.

A date conflict should produce a consistency finding.

71. Timeline and Document Integrity

The Document Integrity Checker should ensure:

timeline file exists;
document version is controlled;
dates are machine-readable where needed;
source links are valid;
registry entries resolve.

72. Timeline and Evidence

A timeline update should produce evidence such as:

legal source;
legal review;
affected artifacts;
change record;
approval;
updated version.

This enables an auditable regulatory-change trail.

73. Timeline and Regulatory Change Management

Recommended process:

New Amendment
      ↓
Legal Review
      ↓
Timeline Change
      ↓
Impact Assessment
      ↓
Mapping Changes
      ↓
Control Changes
      ↓
Evidence Changes
      ↓
Assurance
      ↓
Management Review

74. Timeline and Continuous Improvement

Repeated timeline discrepancies should generate improvement actions. Potential improvements:

automated date checks;
centralized registry;
rule-version control;
source monitoring;
release gates;
timeline validation.

75. AIGO Operational Status Model

For every regulated AI requirement, AIGO should support:

NOT_REVIEWED
REVIEWED
NOT_APPLICABLE
FUTURE_APPLICABLE
CURRENTLY_APPLICABLE
TRANSITIONAL
IMPLEMENTED_EARLY
IMPLEMENTED
EVIDENCED
ASSESSED
ASSURED
SUPERSEDED

The legal status and implementation status should be stored separately.

76. Example Combined Record

Requirement:
Chapter III Sections 1–3

Classification:
Article 6(2) / Annex III

Legal Application Date:
2 December 2027

Current Date:
14 August 2026

Legal Status:
FUTURE_APPLICABLE

AIGO Readiness:
IMPLEMENTED_EARLY

Evidence:
Available

Assurance:
Scheduled

This demonstrates why a single status field is insufficient.

77. Timeline Review Board

Material timeline changes should be reviewed by:

Legal/Compliance;
AI Governance;
Framework Architecture;
affected Control Owners;
Evidence Owner;
Assurance.

The review should determine whether the change affects operational requirements.

78. Timeline Release Gate

Before release of any EU AI Act mapping package, verify:

Current EUR-Lex source checked
Current amendments checked
Application dates checked
Transition dates checked
Public-authority rules checked
Significant-change rules checked
Mapping consistency checked
Registry updated
Legal review completed where required

79. Timeline Review Triggers

Immediate review is required after:

AI Act amendment;
Digital Omnibus amendment;
Article 5 change;
Article 50 change;
GPAI change;
high-risk application-date change;
new transitional rule;
public-authority rule change;
new supervisory provision.

80. Current Baseline Summary

As of 14 August 2026:

1 Aug 2024
AI Act entered into force
        ↓
2 Feb 2025
Chapters I and II generally apply
        ↓
2 Aug 2025
Governance + GPAI apply
        ↓
27 Jul 2026
Digital Omnibus amended provisions enter into force;
Articles 102–110 apply
        ↓
2 Aug 2026
General AI Act application;
Article 50 current
        ↓
2 Dec 2026
New Article 5 provisions;
certain pre-existing synthetic-content transition deadline
        ↓
2 Dec 2027
Annex III high-risk Chapter III Sections 1–3
        ↓
2 Aug 2028
Annex I high-risk Chapter III Sections 1–3
        ↓
2 Aug 2030
Public-authority high-risk transition deadline

The dates above reflect the current amended Article 111 and Article 113 baseline.

81. Legal and Operational Disclaimer

The timeline is intended to support AIGO governance and planning. It should not be used as a substitute for determining the legal applicability of a particular AI system. Specific applicability may depend on:

actor;
system;
intended purpose;
jurisdiction;
market status;
product legislation;
exceptions;
significant changes;
transitional provisions;
sectoral law.

82. Relationship to Other EU AI Act Mappings

File	Relationship
`01-AIGO-EU-AI-Act-Mapping-v0.1.md`	Master mapping
`02-AIGO-EU-AI-Act-Prohibited-AI-Practices-Mapping-v0.1.md`	Article 5
`03-AIGO-EU-AI-Act-High-Risk-AI-Mapping-v0.1.md`	High-risk
`04-AIGO-EU-AI-Act-Transparency-Mapping-v0.1.md`	Article 50
`05-AIGO-EU-AI-Act-GPAI-Mapping-v0.1.md`	GPAI
`06-AIGO-EU-AI-Act-AI-Literacy-Mapping-v0.1.md`	Article 4
`07-AIGO-EU-AI-Act-Governance-and-Enforcement-Mapping-v0.1.md`	Governance
`08-AIGO-EU-AI-Act-Conformity-and-Documentation-Mapping-v0.1.md`	Conformity
`09-AIGO-EU-AI-Act-Rights-and-Remedies-Mapping-v0.1.md`	Rights
`10-AIGO-EU-AI-Act-Annexes-Mapping-v0.1.md`	Annexes
`12-AIGO-EU-AI-Act-AIGO-Control-Mapping-v0.1.md`	AIGO controls
`13-AIGO-EU-AI-Act-Evidence-and-Assurance-Mapping-v0.1.md`	Evidence / assurance

This document is the authoritative timeline source for all of them.

83. Relationship to AIGO Schemas

Timeline Activity	AIGO Schema
Regulatory applicability	Assessment
AI-system classification	AI System / Assessment
Risk impact	Risk
Timeline control	Control
Regulatory approval	Approval
Deadline monitoring	Monitoring
Regulatory incident	Incident
Timeline change	Change
Assurance	Assurance
Timeline evidence	Evidence
Management review	Management Review
Regulatory improvement	Improvement
Historical lifecycle	Retirement

84. Relationship to AIGO Tools

The timeline should be validated by:

Schema Validator;
Reference Validator;
Traceability Validator;
Framework Consistency Checker;
Document Integrity Checker;
Repository Health Checker.

The Control Coverage and Evidence Coverage Validators should use timeline status when determining current versus future obligations.

85. Document Control

Field	Value
Document	AIGO EU AI Act Applicability and Timeline
Version	0.1
Status	Draft
Document Identifier	`AIGO-MAP-EUAI-011`
Document Type	EU AI Act Mapping
Primary Timeline Provision	Article 113
Transitional Provision	Article 111
Current Amendment	Regulation (EU) 2026/1744
Owner
Legal/Compliance Reviewer
Governance Reviewer
Framework Architect
Approved By
Effective Date
Next Review Date

86. Document Status

Document: AIGO — EU AI Act Applicability and Timeline Version: 0.1 Status: Draft Working Name: AIGO Full Name: AI Governance Operating Framework Document Identifier: AIGO-MAP-EUAI-011 Document Type: EU AI Act Mapping This document defines the authoritative AIGO applicability and timeline model for the EU AI Act, including entry into force, phased application, Article 5, AI literacy, governance, GPAI, Article 50 transparency, high-risk AI, conformity-related timing, transitional rules, significant-change rules, public-authority deadlines, and the 2026 Digital Omnibus amendments. End of Document

​AIGO — EU AI Act Applicability and Timeline

​1. Document Purpose

​2. Mapping Information

​3. Authoritative Timeline Principle

​4. Entry Into Force of the AI Act

​5. Digital Omnibus Entry Into Force

​6. Master Timeline

​7. 1 August 2024 — Entry Into Force

​8. 2 February 2025 — Chapters I and II

​9. AI Literacy — 2 February 2025

​10. Original Article 5 Prohibitions — 2 February 2025

​11. New Article 5 Provisions — 2 December 2026

​12. 2 August 2025 — Governance Rules

​13. 2 August 2025 — GPAI Obligations

​14. 2 August 2026 — General Application Date

​15. Article 50 Transparency — 2 August 2026

​16. 2 December 2026 — Pre-Existing Synthetic Content

​17. 2 December 2027 — Annex III High-Risk AI

​18. 2 August 2028 — Annex I High-Risk AI

​19. High-Risk Timeline Architecture

​20. Public-Authority High-Risk Systems — 2 August 2030

​21. High-Risk Systems Placed on the Market Before Chapter III Application

​22. Significant-Change Trigger

​23. Significant Change and AIGO Change Management

​24. 27 July 2026 — Articles 102–110

​25. Timeline Categories

​26. Entry Into Force Versus Application

​Entry Into Force

​Entry Into Application

​Enforcement Availability

​Transitional Deadline

​27. Regulatory Timeline Record

​28. Recommended Timeline IDs

​29. Core Timeline Records

​30. Application Status as of 14 August 2026

​Currently Applicable

​Future

​31. AIGO Current-State Rule

​32. Applicability Decision Algorithm

​33. Applicability Status Examples

​Example A — Article 4 AI Literacy

​Example B — Annex III High-Risk Obligation

​Example C — Annex I High-Risk Obligation

​34. Early-Readiness Status

​35. Early Implementation Rule

​36. Mapping Document Rule

​37. No Duplicate Timeline Authority

​38. Timeline Change Control

​39. Regulatory Change Example

​40. Timeline and Control Activation

​41. Timeline and Assessment Activation

​42. Timeline and Approval

​43. Timeline and Monitoring

​44. Timeline and Incident Management

​45. Timeline and Change Management

​46. Timeline and Management Review

​47. Timeline and Assurance

​48. Timeline Evidence

​49. Transition Evidence

​50. Grandfathering and Existing Systems

​51. Pre-Existing High-Risk Systems

​52. Public-Authority Systems

​53. Public-Authority Flag

​54. Timeline and Annex XIV

​55. Timeline and GPAI

​56. Timeline and Transparency

​57. Timeline and Prohibited AI

​58. Timeline and AI Literacy

​59. Timeline and Governance

​60. Timeline and Enforcement

​61. Timeline and Regulatory Authorities

​62. Regulatory Date Source Control

​63. Timeline Source Currency

​64. Current Legal Sources

​Regulation (EU) 2024/1689

​Regulation (EU) 2026/1744

​European Commission AI Act Regulatory Framework

​European Commission AI Act FAQ

​65. Timeline Registry

​66. Timeline Validation