Coriqo
EU AI Act ยท high-risk

Your December 2027 high-risk record starts now, or it does not exist.

The Digital Omnibus moved the Annex III deadline to December 2, 2027. It did not change what the obligations ask for. Article 12 wants events logged automatically over the system’s lifetime. Article 14 wants oversight built so a person can step in, and evidence that it works. Annex IV wants documentation that tracks the system as it changed. Each of these is a claim about the past. A project started in late 2027 cannot create the past.

Dates reflect Regulation (EU) 2026/1744, the Digital Omnibus on AI, in force July 27, 2026. Annex III high-risk moved to December 2, 2027 and product-embedded Annex I systems to August 2, 2028. Article 50 transparency was not postponed. It applied on August 2, 2026.

The obligations

Four duties you can only meet as events happen

You can meet most of the high-risk rules by writing a good document. You cannot meet these four that way. Each one says something about what was true at a moment that has already passed.

Automatic recording of events over the lifetime of the systemArt. 12
Logs are the easy part. Letting a reviewer confirm the log still reads as it did between the event and the audit is the part few teams have planned for.
Human oversight, effective in practice rather than on paperArt. 14
An oversight policy proves a policy existed. A record of interventions proves oversight happened. It shows who reviewed what, when and what they decided.
Technical documentation kept up to dateAnnex IV
"Up to date" only means something over time. You need to know what the documentation said before each change, not only what it says now.
Post-market monitoring and serious-incident reportingArt. 72, Art. 73
The 15-day reporting clock starts when you became aware. Your own record is what establishes that date, to a regulator and to your insurer.
How it works

A record a notified body can check for itself

Your assessor and your own board should be able to see that a person could intervene, and did, on the date the record says. Your team’s account is stronger when they can check it themselves. Coriqo adds each governance event to a tamper-evident log as it happens. Events include a risk classification, a human-oversight intervention and a model or dataset change. Each entry is linked to the one before it. At regular intervals the log is sealed with a signed checkpoint. The assessor receives the record with a proof that each entry is in the log, the source code of the verifier and Coriqo’s public key. By default each seal is also logged in Sigstore’s public Rekor log, so the assessor can confirm it was not rewritten later.

So you do not ask your assessor to accept that your documentation was written at the time. You hand them the means to check it. The check shows any change made after sealing, though it cannot show an event that was never recorded. We are confident enough in this to publish the bundle and invite people to break it.

The calendar

Where you are on the AI Act timeline

The Act arrives in stages, and each stage assumes the evidence from the one before it. The Omnibus delay moved two of those stages and left the rest where they were. So the useful question is what should already be building up for December 2027.

Dates come from Coriqo’s regulatory library and are for orientation, not legal advice.

Prohibitions and AI-literacy duties applied from February 2, 2025, GPAI model obligations from August 2, 2025, and Article 50 transparency from August 2, 2026. Under the Digital Omnibus on AI, Annex III high-risk obligations apply from December 2, 2027 and product-embedded Annex I systems from August 2, 2028.

Find out what your assessor would find

A 20-minute readiness review against Articles 9 through 15 and Annex IV. We cover what evidence you are already building up, what you would have to reconstruct, and which gaps get more expensive the longer they run. No slide deck, and no separate discovery call first.

We use your address to send the review and to follow up once. We do not add you to a mailing list, send a sequence of emails, or pass your address on.