Skip to content
AIAssuranceLabs
Menu

Regulation change log

This log records every change to the regulatory data behind the site: what changed, the source it rests on, and which pages were updated. Every application date and status shown on the site comes from one data file. A change enters that file only through a scripted update that carries a source URL and appends an entry to this log. The current state is read on the timeline and the standards table.

Entries

  1. Changed on artificialintelligenceact.eu

    art6-3-registration: unsettled-resolver selected the working reading at Stage D (streamlined Art. 49(2) registration applies now; stricter reading, evidence balanced); status verify to decided, decidedBy set. Both readings and sources in data/unsettled.json; DECISIONS.md entry tagged ASSUMED.

    Entries
    Pages updated

  2. Changed on artificialintelligenceact.eu

    art10-sensitive-data-threshold: item label now names Art. 4a, where the Omnibus placed the legal basis after deleting Art. 10(5); the entry id, date and the publisher's working reading are unchanged. Seed conflict 2 in review/00-regulation.md resolved by the main session.

    Entries
    Pages updated

  3. Changed on artificialintelligenceact.eu

    ai-literacy: date corrected from the seed's 2 August 2026 to 2 February 2025, the Chapter I application date under Art. 113(a); the amended Art. 4 wording applies from the Omnibus entry into force. Seed conflict 1 in review/00-regulation.md resolved by the main session.

    Entries
    Pages updated

  4. Changed on digital-strategy.ec.europa.eu

    Initial verification of all sixteen seed entries from inputs/regulatory-anchor.md against the Commission timeline, the post-Omnibus consolidated text (AI Act Explorer rendering; EUR-Lex unreachable) and law-firm briefings dated after the Omnibus entry into force. Thirteen entries confirmed; ai-literacy flagged as a date conflict (seed value kept); art10-sensitive-data-threshold flagged because the provision moved from Art. 10(5) to Art. 4a (working reading kept); art6-3-registration set to verify per the regulation skill.

    Entries
    Pages updated

How a change is made

The regulation verifier re-checks each entry against the consolidated text of Regulation (EU) 2024/1689 as amended through Regulation (EU) 2026/1744 and against law-firm briefings published after the Omnibus entry into force. The verifier has no scheduled run; it is run when a change in the law or in a standard becomes known. An entry that matches keeps its value and receives a new verified-on stamp. An entry that differs is flagged as a conflict in the review record, and the resolution is applied with the update script, which refuses a change without a source URL.

Each log entry names the regulation entries it touched, linked to their rows on the timeline, and the pages updated as a result. A change to an application date reaches every page that renders that entry, including the obligation pages and the obligation tracker, because those pages read the same file at build.

The standards table on /standards/ is re-verified in the same run: each draft, enquiry, approval and published stage is checked against the standards body or its tracker, and the count of harmonised standards cited in the Official Journal is recounted. As of the anchor date that count is zero, so no entry on the site carries a presumption of conformity: none is cited in the Official Journal yet. The stamp below marks the current run.

Verified on last full verification run, see the change log

A reader who finds a discrepancy between an entry on this site and the consolidated text can write to the address on /contact/ with the entry id and the source; a confirmed discrepancy is corrected through the same script and appears in this log.