Mr. Federico Sturzenegger, Minister of Deregulation and State Transformation:
On April 28 at Expo EFI you announced the regime, and on June 1, 2026 the Executive sent the Senate the draft bill that replaces Law 19.550. It creates the Sociedad Automatizada (art. 14): a company run by AI agents, with no employees on payroll for its ordinary operation, that answers with its own assets and keeps an administrator who configures and supervises the system (art. 102). And the Sociedad Descentralizada Autónoma Operativa(DAO, art. 258), with a mandatory human legal representative (art. 260). Your quote was clear, “if in 10 years 90% of global GDP is produced by AI agents, we want that legal regime to be in Argentina”.
I'm writing to tell you I've built the technical layer that regime will need. When I read your announcement, I started right away. This is what exists today, publicly, on npm and GitHub, under MIT license:
- 36 packages under the
@ar-agents/*scope on npm. - 235 tools with verified type definitions for Vercel AI SDK 6, the industry-standard toolkit for agents.
- 16 of the 17 operational pieces an Argentine AI corporation will need to operate: identity (CUIT, ARCA, RENAPER, Mi Argentina), digital signature (Law 25.506, ONTI), money (Mercado Pago + AFIP electronic invoicing + BCRA Central de Deudores + Key Variables), customer ops (WhatsApp Business, Andreani, OCA, Correo), state monitoring (Official Gazette, datos.jus.gob.ar for IGJ).
- SLSA v1 provenance attestations (proof that the code published on npm is the same as on GitHub, unaltered) on every release. MIT. No upfront cost. No proprietary dependencies under the hood.
One piece is missing: @ar-agents/gde-tad complete, integrated with real IGJ registration. It depends on the state opening a documented API for TAD. Today there is a functional adapter for incorporation pre-flight and for the Electronic Domicile inbox, but the constitutive deed cannot be filed programmatically. If the new General Companies Law passes Congress with a technical mandate to expose TAD programmatically, the cycle closes.
Why I'm writing this
I'm writing because I'm aligned with the proposal of treating Argentina as an experimental jurisdiction for AI agents. For the plan to work, the reference implementation has to exist and be verifiable. A company from any country weighing whether to incorporate in Argentina will look for two things: the legal text and the code that connects an agent-company to the state. The legal text depends on the government. The code can be written by any qualified citizen. That is what I did.
What might be useful to you
/video: 2:30 minutes of an agent using 6 ar-agents packages to incorporate and operate a fictional Argentine AI corporation from start to finish. The fastest way to see what this is about without reading code./en/ai-corporations: the map of the 17 operational pieces and a real-agent transcript executing the “incorporate + operate” cycle in ~12 seconds. Reusable for presentations./rfcs/001: RFC on identity, signing, and liability of agents in Argentina (CC-BY-4.0, DOI 10.5281/zenodo.20159396). The technical questions the proposal will have to answer, with concrete proposals. Ready for an advisor to copy into a Ministry document if useful./en/implementation: the technical document for the bill drafting team. Architecture on preexisting open standards, five suggested operable clauses for the text, and answers to the legal objections from the public debate. MIT, citable, for circulation in the Ministry's technical areas.
My proposal
A point for the legislative debate: the most predictable objection to the bill will be that building the technical infrastructure for AI corporations is expensive and slow. The reference implementation enclosed shows the opposite. It already exists, is functional, audited, and available under MIT license. The regime does not start from zero; it starts from a stack that already operates.
What would be useful:
- That the ministry knows the reference implementation exists while the draft bill is debated in the Senate. That way the final text doesn't drag in technical assumptions that contradict a stack that already works, and the regulation that arts. 263-264 leave pending moves faster.
- That TAD (Trámites a Distancia) expose a documented API for registrations. Without it, the last piece doesn't close. I can help with this too.
- If any technical team (Subsec TIC, the Sandbox team, or another) finds it useful to read RFC-001 and comment, public comments on GitHub are welcome.
I remain at your disposal.
Sincerely,
Nazareno Clemente
Argentine Software Engineer.