AI Act, Cyber Resilience Act, Résilience bill: the same missing inventory
Three European texts fall on the same calendar, with opposite effects on demand: one has just been postponed by eighteen months, another applies in six weeks, the third holds budgets back until it is passed. What they require, however, is very similar.
These texts are often discussed as a single block, “compliance”, and the dates that matter get missed as a result. They do not move in the same direction. On 1 August 2026, one has just been postponed, another falls due in six weeks, and the third has still not been adopted. An independent worker planning around the regulatory calendar therefore needs to read it text by text.
The European regulation on artificial intelligence was due to impose its obligations for “high-risk” systems from 2 August 2026, which is tomorrow. The simplification regulation known as the Digital Omnibus, in force since 27 July, has postponed them to 2 December 2027 for stand-alone Annex III systems, and to 2 August 2028 for AI built into products that are already regulated. The stated reason is the delay in harmonised standards and in the designation of national authorities.
On 2 August 2026, what remains is the transparency obligation: informing a person that they are dealing with a machine. It is real, but light. The governance, audit and documentation work that the date was expected to generate has been pushed back eighteen months. That is market information more than legal information, and the budgets planned for this summer will be spent elsewhere.
The cyber resilience regulation sets its first binding deadline on 11 September 2026: any manufacturer of a product with digital elements must report actively exploited vulnerabilities and serious incidents. The time limits are those of an on-call rota: early warning within twenty-four hours, detailed notification within seventy-two hours, final report within fourteen days. The main obligations follow on 11 December 2027, with penalties of up to fifteen million euros or 2.5 % of worldwide turnover.
The twenty-four-hour limit is decisive, because it turns a legal obligation into an engineering problem. You cannot report an actively exploited vulnerability within a day without knowing what your product contains: which libraries, in which version, in which delivered version of the product, at which customers. That question is about inventory more than law.
The French transposition of the European cybersecurity directive, carried by the bill known as Résilience, would increase the number of entities subject to obligations from about five hundred to fifteen thousand. Passed by the Senate in March 2025, it has been postponed several times, and it is expected to be examined in the autumn. Until it is passed, its effect is the opposite of what is assumed: management waits for the text before deciding, and demand stays on hold.
These three texts ask for the same thing, each in its own vocabulary. The cyber resilience regulation requires an up-to-date software bill of materials, a stated support period and a history of fixes. The AI regulation requires, for a high-risk system, knowing what data it was trained on, what it produces and what was logged. The cybersecurity directive requires an entity to know which systems it runs and which of them are critical.
In all three cases, what is needed is an inventory that is kept up to date, dated, queryable and matched against what is actually deployed. This is a data problem more than a legal or security one: collection, freshness, joining two registers that share neither granularity nor cut-off date. It is the difficulty described elsewhere on this site in relation to public files, and it is handled in the same way.
That is also why I am wary of the idea that these texts mainly create a market for legal advice. The part that falls to a lawyer is short and dealt with once: am I in scope, and on what basis? The lasting part is producing, every day, an exact picture of an estate at a given date, without anyone keeping it up by hand, and no legal memo has ever solved that problem.
I am not a lawyer, and nothing above says whether you fall within the scope of any of these texts. That is the one question that requires qualified advice, and I do not address it. Nor do I cover the harmonised standards, whose absence justified the July postponement. They will define in practice what “compliant” means, and they have not yet been written.
One last reservation, about how long this article remains valid. It is dated 1 August 2026 because one of these dates changed four days earlier. A text that postpones its own deadlines can do so again, and the calendar above is valid as of that date. I keep these deadlines current on legal.commutator.io, which is updated, whereas this page will not be. If the two differ, the tool is the reference.