Featured

States and municipalities must share their systems' code with the ATDT (federal digital agency), even if a vendor built it, and since September 28 adopt its models for procedures

Translated from the Spanish original.

ContradictionTecnologías EmergentesLong term

On September 28, 2026, the Agencia de Transformación Digital y Telecomunicaciones (ATDT, Digital Transformation and Telecommunications Agency) published in the DOF (Mexico's federal gazette) the notice by which its Modelos para la Homologación de Trámites y Servicios (Models for the Standardization of Procedures and Services) become binding on all three levels of government; they must be adopted within no more than thirty business days. The model's guidelines, published on September 2 and in force since the following day, allow one hundred twenty business days to implement them once adopted and establish that regulatory harmonization "may in no case obstruct" implementation. Among the obligations of local authorities is sharing with the Repositorio Nacional de Tecnología Pública (National Public Technology Repository) the source code of their technology solutions, developed "by themselves or through third parties", so that other obligated entities can use and modify it; if there is an intellectual property dispute, the local authority must "hold harmless" the national authority. Whatever becomes part of the repository cannot be commercialized.

Strategic interpretation

Systemic: Municipal software in Mexico has been bought as a product: a vendor builds the property-tax or licensing system and sells it to several municipalities. The ATDT (federal digital agency) redefines it as a common good: what one government uses, the others can use. The tension is between public technological sovereignty, which needs the code, and existing contracts, which in many cases probably leave the intellectual property (IP) with the vendor (no published count). The rule loads that tension onto the weakest link: the municipality is liable if it shares code not its own. It reaches what was developed "through third parties"; whether it reaches software the vendor only licenses is the first question contracts will settle. The ATDT wins, building a national pool from what others paid for, as does the small municipality; the integrator that resells the same solution loses. Consequence: It falls on the mid-sized software vendor for local governments and on municipal IT and legal departments, which must review who owns what they bought. What follows: new contracts will require code assignment, and the price will pay for a service rather than a license. Three to ten years out: either a public pool consolidates that makes digitizing a municipality cheaper, or the legal burden produces the opposite: municipalities that stop commissioning their own development so as to have nothing to share. Worldview: That the government is just another customer in the software market and that what it pays for with public money can remain private property. What to watch: How many governments publish their adoption agreement when the thirty business days expire—around November 10, own calculation—and how many solutions appear in the repository in 2027; whether a vendor brings the first IP dispute against a municipal government; and whether 2027 municipal contracts require code assignment. Ten years out: whether public municipal software is a common pool or a lawsuit.

Sourcehttps://dof.gob.mx/nota_detalle.php?codigo=5799710&fecha=28/09/2026

ATDT (Digital Transformation and Telecommunications Agency), notice publishing the Modelos para la Homologación de Trámites y Servicios (Models for the Standardization of Procedures and Services), DOF (Mexico's federal gazette), September 28, 2026 (code 5799710). Lineamientos para la Implementación del Modelo Nacional de Homologación de Trámites y Servicios, Compartición de Soluciones Tecnológicas y Desarrollo de Capacidades Públicas (Guidelines for Implementing the National Model for Standardizing Procedures and Services, Sharing Technology Solutions and Developing Public Capacities), DOF, September 2, 2026 (code 5797724), Articles 26, 27, 32, 33, 35 and 36 and the obligations of local authorities. Both accessed and cross-checked on October 19, 2026. The model catalog (catalogounico.gob.mx) did not open via script, so it is not known how many procedures it includes.

Chapter signal radar

Published on October 20, 2026