AI Regulation Tracker / Provincial decree
Buenos Aires Province Sets Binding Rules for Public-Sector AI With Decree 742
On July 14, 2026, the Province of Buenos Aires published Decree 742/2026 in its official gazette, a binding framework for how the provincial government develops, buys and runs artificial intelligence, built around a prior-intervention step, a public-sector AI registry and a risk and impact review.
On July 14, 2026, the Province of Buenos Aires published Decree 742/2026 in its official gazette, approving a framework for how the provincial state develops, uses and governs artificial intelligence. It was signed by Governor Axel Kicillof and countersigned by the Minister of Government, Carlos Bianco. The Subsecretaria de Gobierno Digital, which sits inside the Ministerio de Gobierno, is named as the authority in charge of applying it.
What the decree actually does
Strip away the modernization language and the decree does a handful of concrete things.
First, it puts a gate in front of every AI project. No ministry, decentralized entity or autonomous body can develop, contract, implement or put an AI system into operation without the prior intervention of the Subsecretaria de Gobierno Digital. In plain terms, the digital government office now sits between a provincial agency and any AI system that agency wants to stand up. That is a real, mandatory review step, not a suggestion.
Second, it creates a Registry of Artificial Intelligence. Every provincial body that develops or uses an AI system has to register it and keep the entry current with the system's characteristics, its status, any modifications and other relevant information. The province is building an inventory of where AI is being used inside its own walls, which is something most governments cannot produce on demand today.
Third, before a system is switched on, the framework requires a risk and impact assessment. Reporting on the decree describes that assessment as looking at effects on fundamental rights, the quality of the training data, the risk of bias, the labor consequences of putting the system into service, and the environmental and energy footprint of running it. That last item is worth noting. Energy and labor impact are not standard fixtures in AI rules elsewhere, and their presence tells you something about the political frame this decree was written in.
Fourth, it keeps a human in the loop. The framework leans on principles of ethical, transparent and people-centered use, with human oversight of decisions and traceability of automated processes. The stated posture is that AI in the provincial state is an assistance tool that extends the capacity of public employees, not a replacement for them.
Finally, it sets up an advisory council, described as interdisciplinary and multisectoral, drawing in specialists and universities to issue recommendations and reports on public-sector AI use. That is the part that will shape how the principles get interpreted over the next few years.
Be precise about the scope
This is where a lot of coverage will blur, so I want to be exact.
Decree 742/2026 is a provincial instrument, and it governs the public sector. Its reach is the administration of the Province of Buenos Aires: central administration, decentralized and autonomous entities, constitutional bodies, and state-owned companies. Municipalities within the province are invited to adhere on their own terms, according to each district's competencies. They are not forced in.
It is not a national law. Argentina's federal government and its Congress have their own separate AI conversations, and this decree is not one of them. It is not a private-sector AI statute either. If your company is not building AI for the Buenos Aires provincial state, this decree does not impose obligations on you directly. And it is not the European model of tiered, economy-wide AI risk regulation. It is a government putting rules on its own use of a technology.
I am drawing that boundary hard on purpose. It is easy to read "Argentina's biggest province regulates AI" and assume a broad new compliance regime just landed on every business operating there. It did not. What landed is a public-sector governance framework with procurement teeth.
What changes for operators and public-sector vendors
If you sell AI, or AI-enabled services, into the Buenos Aires provincial government, treat this as a change in the buying process, because that is what it is.
The prior-intervention requirement means your buyer inside a ministry can no longer just sign a contract and deploy. The system has to pass through the Subsecretaria de Gobierno Digital first. Deals that used to close at the agency level now have a central checkpoint, which can affect the timing and conditions for deployment. Build that review into your timeline and your pipeline forecasts rather than discovering it at signature.
The registry requirement means your system becomes a documented, inspectable entry in a provincial inventory. Expect procurement to ask you for the material that populates that entry: what the system does, what data trains it, how it is maintained, and what changes when you push an update. Vendors who can hand over clean documentation will move faster than vendors who cannot.
The risk and impact assessment is the part that will separate serious bidders from the rest. The province will want evidence on fundamental-rights impact, data quality, bias, labor effects and energy use. If you already run model documentation, bias testing and data-provenance records, you are most of the way there. If you do not, you now have a concrete reason to start, because a buyer is going to ask.
Two more practical points. The human-oversight principle means you should not pitch full automation of decisions that affect residents. Position your product as decision support with a person accountable at the end. And the data-handling expectations mean you should be ready to speak to how the province's data is protected inside your system, including retention and access, before anything sensitive goes near it.
For operators outside that procurement relationship, the value here is directional. A large Latin American government has now written down, in a binding instrument, the exact controls it expects around AI: a gatekeeper, a registry, a risk assessment, human oversight, and an advisory body. Other provinces and other governments in the region tend to borrow from each other. This is a reasonable preview of the questions your public-sector customers across Latin America will start asking.
What to do now
If your business touches the Buenos Aires provincial state, a short list.
Pull the actual decree text from the provincial Boletin Oficial and have someone who reads Spanish and understands Argentine administrative law walk through it. The reporting is consistent, but contracts get written against the operative text, not against news summaries. Confirm the exact obligations, any transition periods, and how the prior-intervention step is meant to work in practice.
Map your current and pending provincial deals against the new prior-intervention step. Identify which ones now need Subsecretaria de Gobierno Digital prior intervention and adjust the timelines you are promising internally and to the buyer.
Assemble the documentation package the registry and the risk assessment will demand: system description, data sources and quality, bias testing, maintenance and change logs, human-oversight design, and a data-protection write-up. Get it ready before a tender asks for it.
If you operate elsewhere in Latin America's public sector, file this as a leading indicator and check whether your own government customers are drafting something similar. It is cheaper to build the documentation habit now than to retrofit it under a deadline later.
Questions professionals are asking
Is Decree 742/2026 a national Argentine AI law?
No. It is a decree of the Province of Buenos Aires, and it governs the provincial public administration. It is not a national statute, and Argentina's federal AI debates are separate from it. It also does not regulate private companies across the economy.
Who has to comply, and can my company be forced to follow it?
The binding scope is the provincial public administration: central administration, decentralized and autonomous entities, constitutional bodies, and state-owned companies. Municipalities may adhere voluntarily. Private companies are not directly bound, but if you sell AI into the provincial government you will feel it through procurement, because the systems you supply have to clear approval and be registered.
What are the main obligations the decree creates?
Prior approval by the Subsecretaria de Gobierno Digital before any provincial body develops, contracts or deploys an AI system; registration of each system in a provincial AI registry; a risk and impact assessment before a system goes live; human oversight and traceability of automated decisions; and an advisory council to issue recommendations.
Where can I read the official text?
In the Boletin Oficial de la Provincia de Buenos Aires at boletinoficial.gba.gob.ar. Use the Buscador de normas and search for Decreto 742/2026. Treat that gazette text as authoritative over any news summary, including this one.
Does it apply outside the Province of Buenos Aires?
Not directly. Its legal reach stops at the provincial administration, with an open door for municipalities that choose to adhere. Its usefulness beyond the province is as a signal of the controls Latin American public-sector buyers are starting to expect around AI.
RELATED BRIEFINGS
Browse the full AI Regulation News tracker
Informational analysis for working professionals, not legal advice. Confirm how any rule applies to your situation with qualified counsel in the relevant jurisdiction.