AI Regulation Tracker  /  Pre-legislative signal

Ukraine Has Started Drafting an AI Law, and That Is All It Has Started

The Ministry of Digital Transformation says the first meeting of the working group on legal regulation of AI has been held and that a law synchronised with EU rules will be produced during 2026. Nothing is binding today. The date to diary is the Cabinet's own Q4 2026 deadline for a draft to reach ministers.

By Anthony Guerriero  ·  Reviewed by Anthony Guerriero  ·  Published August 3, 2026  ·  Updated August 3, 2026  ·  Pre-legislative signal

Key facts

Regulatory briefing

Instrument

Government announcement of the first meeting of the working group on legal regulation of AI, and preparation of a dedicated EU-integration law on artificial intelligence. No draft text accompanies it

Authority

Ministry of Digital Transformation of Ukraine; statement attributed to Oleksandr Bornyakov, acting Minister of Digital Transformation

Jurisdiction

Ukraine

Status

Pre-legislative. Drafting phase opened; no bill text and no Verkhovna Rada registration identified in the sources reviewed as of August 3, 2026

Bindingness

Not binding. Draft or proposed only

Effective date

None. The nearest fixed milestone is the Q4 2026 submission deadline in Cabinet of Ministers Ordinance No. 457-r of May 9, 2025

Primary source

Ministry of Digital Transformation of Ukraine, June 15, 2026

What the ministry actually said, and what it did not

Start with the thing itself, because the gap between the announcement and the coverage of the announcement is where most readers will get into trouble. On June 15, 2026 the Ministry of Digital Transformation published a post whose subject is a meeting. The first meeting of the working group on legal regulation of AI had taken place, the acting Minister summed up the ministry's work in the field, and he set out the next step as the creation of a dedicated EU-integration law.

The operative passage reads:

Україна успішно проходить етап підготовки та саморегуляції та готова до чітких законодавчих правил. Протягом 2026 року спільна робоча група розробить закон про штучний інтелект, який врахує інтереси суспільства, держави та бізнесу. Цей закон синхронізує наше поле з правилами ЄС.Ministry of Digital Transformation of Ukraine, June 15, 2026

In our translation: Ukraine is successfully completing the preparation and self-regulation stage and is ready for clear legislative rules; during 2026 a joint working group will develop a law on artificial intelligence that takes account of the interests of society, the state and business; this law will synchronise our field with EU rules.

Now the negative space, which matters more. There is no draft text attached. There is no bill number, because no AI bill was found registered in the Verkhovna Rada in the sources reviewed as of August 3, 2026. The post does not name the working group's membership, does not give it a founding decree, and names no chair other than Bornyakov, who is the acting Minister and the only official identified. It does not state the date on which the meeting was held; the June 15 date is the date of the ministry's own publication. And no national AI competent authority, market surveillance authority or notifying authority was identified in the national sources reviewed as of August 3, 2026.

So the honest description is narrow: a ministry has said out loud that it intends to write a law, and has said which rulebook it intends to write toward. That is genuinely useful information. It is not an obligation, a deadline for industry, or a compliance event.

The Cabinet ordinance that puts a date on it

The announcement has no date in it. There is, separately, a government instrument that does.

Cabinet of Ministers Ordinance No. 457-r of May 9, 2025 approves the Action Plan implementing the Concept for AI Development in Ukraine for 2025 to 2026. One item of that plan tasks the Ministry of Digital Transformation with developing and submitting to the Cabinet of Ministers a draft law on legal regulation in the field of AI development, with a deadline of the fourth quarter of 2026 and a performance indicator that the bill be submitted to the Cabinet and then forwarded to the Verkhovna Rada.

I want to be precise about how these two facts relate, because it is easy to fuse them and wrong to do so. The ordinance's text does not mention a working group, and the ministry's post does not cite the ordinance. They are two separately verified items that point in the same direction. Treating the working group as a creature of Ordinance 457-r would be an invention, and the sort of invention that survives into every downstream summary once someone writes it once.

Read together and carefully, they still give a practical planning shape. A government plan approved in May 2025 asked for a draft law by the end of 2026. In June 2026 the responsible ministry said the drafting body has met and that the law will be developed during 2026. If both hold, a text reaches the Cabinet in the last quarter of this year and the Verkhovna Rada sees it after that. Parliamentary passage, transitional periods and the eventual date of application are all downstream of a document that does not exist yet, which is why nobody should be quoting a compliance date for Ukraine.

What Ukraine built while it had no statute

The more interesting content of the ministry's post is the inventory of the preparatory phase it says is now closing. This is where a reader can judge whether the drafting phase has anything behind it.

The regulatory sandbox is the centrepiece. The ministry states it received 90 applications to test AI products in its first year, and that 15 solutions have already passed audit by 23 engaged experts. Take the numbers for what they are, which is a self-reported operational record from the body that runs the programme, rather than an independent evaluation. Read carefully, they are still informative. Ninety applications in twelve months says demand exists. Fifteen audited passes against ninety applications suggests, at least on the ministry's own account, a process that filters rather than one that stamps. And the reference to 23 engaged experts tells you the reviewing is being done by people rather than by a form, which is the difference between a sandbox that produces usable regulatory learning and one that produces a press release.

Second, an AI Terminology Dictionary 2.0 released in 2026 in machine-readable format. That sounds like housekeeping and is not. In my experience the definitions are where AI rules are won and lost: what counts as an AI system, what counts as a general-purpose model, what counts as a high-risk use. Those boundaries decide whether your product is inside or outside a regime, and they are the sentences your counsel will argue over. A ministry that publishes a machine-readable terminology set before it drafts is doing that work in the right order, and machine-readable matters too, because it is the form in which definitions can actually be wired into filings, registers and internal classification tooling rather than retyped by hand.

Third, self-regulation with names on it. The ministry says 14 companies, among them Grammarly, MacPaw, SoftServe and Uklon, formed Ukraine's first organisation for the ethical use of AI. Fourth, the international layer: the ministry states Ukraine has signed the Bletchley Declaration and the Council of Europe Framework Convention on AI, and has run HUDERIA workshops. On the Framework Convention the primary source says signed, and the treaty-status chart could not be opened when checked, so ratification status is unverified in either direction and should not be asserted one way or the other.

Public-sector deployment is the other half of the picture the ministry paints, and to my mind it explains why the state wants a statute at all. The post names the Diia AI assistant, the NVIDIA AI Factory, and a national large language model built with Kyivstar. A government that is itself running citizen-facing models has a supervision problem it cannot answer with a voluntary code, because the deployer and the rule-maker are the same office. Statutory duties, with a named supervisor, are the usual way out of that. It is also the reason I would expect the eventual Ukrainian text to say something specific about public-sector use rather than confining itself to products sold by private firms.

Why a US professional should care about a Ukrainian working group

Because of where the engineering sits. The companies the ministry names in its own post, Grammarly, MacPaw, SoftServe and Uklon, are the profile: engineering-heavy firms with US commercial exposure and Ukrainian build capacity. If your product organisation has a Ukrainian development centre, a Ukrainian outsourcing vendor, or a subsidiary of that type, then a domestic AI statute reaches your engineering pipeline whether or not it ever touches a customer contract. That is the exposure most US compliance registers miss, because they are organised by where revenue is booked rather than by where models are trained and shipped from.

The likely shape is the part worth planning against. The ministry describes the intended law as a dedicated EU-integration measure and says it will synchronise the field with EU rules, which tells you which rulebook to read even though nobody can yet read the text. If the eventual law tracks Regulation (EU) 2024/1689, the vocabulary your Ukrainian entity will have to speak is already familiar: provider and deployer roles, a risk-tiering exercise, prohibited practices, transparency duties for systems that interact with people or generate synthetic content, and a heavier documentation regime for high-risk uses. Note that this is my expectation about a text nobody has read, not a description of anything Ukraine has enacted.

Two things that are true today and often confused. First, EU AI Act obligations are not obligations of Ukrainian law, and should not be described to a Ukrainian subsidiary as though they were. Second, the EU AI Act may nonetheless already reach that subsidiary directly, on its own territorial terms, where output is placed on or used in the Union market. The EU timetable is the fixed one: general application from August 2, 2026, transparency and watermarking duties from December 2, 2026, and high-risk obligations moved by the Digital Omnibus to December 2, 2027 for stand-alone Annex III systems and August 2, 2028 for Annex I embedded systems.

That asymmetry is the practical point. The Union deadlines are real and near. The Ukrainian ones are aspirational and further out. Work the first set, and let the second set inherit the artefacts.

What to do before there is a text

Very little, deliberately. Building a compliance programme against an unwritten statute is how budget gets burned, and I have watched teams do it in three jurisdictions.

What is worth doing is cheap and durable. Know what your Ukrainian entity actually runs: an inventory of models, the ones it builds versus the ones it merely integrates, and which of them produce output that reaches EU or US users. That inventory is the input to every AI regime written so far, and it will not be wasted whatever Ukraine passes.

Set a watch rather than a project. The trigger to act is not another ministry post; it is the appearance of a draft, then a registration number in the Verkhovna Rada, then a first reading. Those are three distinct events and only the third tells you the text is being negotiated in public. Diary the Q4 2026 submission deadline from Ordinance 457-r as a review date rather than as a compliance date, and if the quarter passes without a text, that is information, not a crisis.

If you have an appetite for it, the sandbox is the one live mechanism here. The ministry says it has been running a year and has processed real applications through audit. A firm that wants supervised testing, and wants to be in the room while the people writing the law watch how products behave, has an unusually cheap way in. That is a business development judgement, not a compliance one.

And keep the category straight in your own reporting. When a board paper says Ukraine is regulating AI, someone downstream will read that as a deadline. What Ukraine has done is announce that it will write a rule, and tell you which rulebook it will copy from. Label it a signal, record the source and the date, and revisit it when a text exists.

Last verified: August 3, 2026 against the primary sources listed above.