A New AI Lexicon: Exporting AI
By: Ai Now Institute
Tags: Export, Markets, Machine Learning, AI, Artificial Intelligence

AI/ML models are often exported. For example, large tech companies tend to congregate in particular parts of the world and sell software-as-a-service, platform-as-a-service, even surveillance-as-a-service in neatly-bound packages on a subscription basis to individuals, companies, and authorities around the world [1]. As a service/product/labour, AI/ML systems are also frequently exceptionalized where sleek models are intentionally portrayed to magically appear from thin air, skipping the commodity chain altogether. Software and virtual products are often decoupled from their material entanglements — divorced from the vast lithium farms of the Atacama Desert, the cold data centers underneath the Alps, the data annotation centers scattered across the world, and the digital graveyards in the Korle Lagoon [2], [3].

As a feature of our capitalist society, all global supply chains have hidden components — whether it is the obfuscation of sweatshops that operate on child labor or the efforts made towards washing the blood off of the diamond industry. Much important work focuses on unearthing and redressing the unethical operations that undergird the commodities we rely on — and the same applies to data systems. The apparent immateriality of data and its infrastructures however, add an unintuitive dimension to this project. With more physically tangible exports, like a motor engine, we can more intuitively grasp and communicate that the multiple components that constitute it are designed, assembled, and tested in disparate places. A growing body of literature tackles exactly this, to work against this intangibility of data and tying it to its materiality and redressing the injustices left in the wake of AI/ML system development [4]–[6].

AI/ML systems are peculiar exports in another way. They are never quite finished in the same way that many other exports are, such as freshly bound books or fruits that ripen on arrival. AI/ML systems are exported unfinished, with room to tinker and improve. They are trained and tested in lab settings and then trained and tested again in real world settings — constantly learning on the way — a key feature of the iterative process. The decision of when a system is “ready” for deployment is often difficult to ascertain and sometimes decided based on evaluation metrics or arbitrary comparison to some baseline, other times based on contextual needs and urgency.

Where is AI Made?

The advent of the Internet has seen the rise of “Anything-as-a-Service” which are services that simplify complex programs into plug-and-play systems where user-friendly endpoints are provided for customers to interface with. This can include anything from commercial spyware systems that provide easy-to-use navigation platforms to intercept large amounts of communications, to facial analysis systems that provide a slick interface that supposedly helps deconstruct one’s emotional states — the list is endless[1]. The provider offers continued maintenance, updates, and troubleshooting support where the client does not necessarily need to have technical knowledge of the systems at hand, how it runs, or what data has trained it.

While such systems may appear simple at the user level, the assembly line of AI systems are long and convoluted. Labor, decisions, and expertise are needed at each stage prior to a model’s deployment, and even still after it is deployed. There is however usually a particular point in this process where a model is deemed to be “made” — a stage where the labor is deemed as most important and valued. With Software-as-a-Service, this is usually the end stages of the product’s life cycle where “intelligence” is offered as a slick package, usually “assembled” at the company’s headquarters, such as California’s Silicon Valley or Dublin’s Silicon Docks. It is at this juncture where code and data are assembled to be intelligent and then exported.

This is despite how many vital components that constitute a system exists before this point. Sareeta Amrute and Luis Felipe Murillo in particular have written about the importance of destabilizing the presumed centers of computing such as Silicon Valley, and instead, redirecting our starting point elsewhere, such as in the geographies that have long been associated with the “South” [7]. This includes highlighting the concerted efforts of data engineers, data labelers, data cleaners that live beyond Silicon Valley for instance [5], [8], [9]. Other scholars, such as Rida Qadri and Nina Dewi Toft Djanegara, have also demonstrated the need to look beyond formally employed data workers and towards the host of human intervention needed for these systems to work — whether it is the local knowledge of drivers that makes food delivery platforms functional, or the expertise of passport photo studio operators that make visual data legible to machines [10], [11].

We, too, are also often part of AI/ML systems, even if we do not know it. We could be part of a training model, such as the Google reCAPTCHA “human intelligence task” systems which prompt users to verify that they are human by typing words as seen from an image which would ultimately help Google Books, Google Street View, Google Search and other services to detect text and numbers automatically [12]. We can also be part of the training after deployment, stuck as part of the endless feedback loop where some communities in particular are deemed as testing grounds for technologies [13], [14].

Fig 1: Is a city intelligent, in its emergent ways of learning, adapting, subverting? What is a “smart city” if the city is already smart? Fig 2: Are the great banyan trees intelligent, in its centuries of life — moving, perceiving and learning its surrounding environments through its aerial roots? Fig 3: Is intelligence a cold, metallic blue?

So where is an AI made? What intelligence are we exporting? A disembeded, robotic, metallic intelligence — the intelligence of a few — the intelligence of a thousand people?

AI systems are software and data, but are tied to hardware, and rely on servers, clouds, wires, and people who are simultaneously clients, workers, end-users and data points. Sareeta Amrute and Luis Felipe Murillo highlight the work by post/de-colonial scholarship to examine the obscured labour of computing worlds which are often grouped under the heading of “outsourcing.” This literature examines how the least lucrative jobs in computing are siphoned overseas to peripheral communities (e.g. data labelling and content moderation work). Likewise, the flipside is also deserving of scrutiny: when Western centres of power are the targets of “outsourcing” and when the South becomes reliant on technological services from the West. These under-regulated flows become another way in which imperial dependencies and logics are further entrenched in our systems. AI/ML systems have been touted as a disruption, but in truth, these systems often sit snugly as part of the long, uncomfortable histories of exports and global commodity chains — including the continued patterns of inequitable value extraction and the export of certain ways of doing things.

What jurisdictions are AI tethered to?

While intelligence might be everywhere in the process, the power to frame, gate-keep and benefit off of production of AI/ML systems is less distributed. This includes who owns the various data pipelines and data infrastructures at large. Likewise, it matters which jurisdiction these technologies are governed by and which citizens they are accountable to. For example, where are the complaint procedures and warranties bound to? Whose knowledge, needs, and assumptions are prioritized? Just because intelligence is sourced from all stages of production does not mean power is equitably distributed. While platforms and systems might have a vast user-base and worker-base, the number of people who can, in reality, hold a technology giant accountable — to have their concerns heard and acted on — is far fewer [15], [16].

How do we label AI?

How then, do you label such an elusive, intangible export to truly capture its planetary production process? AI/ML systems appears ill-fitted to many of the categories we are used to thinking through. We are familiar with certain labels, regulations, ways of appraising exports — such as “made in” labels, environmental certifications, ingredients list, or some indication of where the factory that assembled the product is located. We have some intuition as to how to trace the likely source of a faulty engine part or a crate of wine that is not quite up to standard. We can find out which publisher to call up when we find inaccuracies in a manuscript. This is not to say other exports are not problematic or that labels are in any way perfect (for instance, see critiques of Fairtrade standards[1]). Nevertheless, it appears increasingly important to explicate the supply chains in our data systems. How do we assess whether an AI/ML system or its end products uses fair labor, to which jurisdiction it is accountable to, or what their environmental effects are?

Although, like other exports, it is important that our labels, categorizations and imaginaries elucidate rather than obscure. Carbon footprint labelling are becoming more common as we are forced to contend with the ecological consequences of large scale AI/ML systems² [17]. An example ML carbon footprint calculator is³:

Carbon footprints are discussed alongside “carbon offset” — ways to compensate for carbon footprint by funding carbon reduction projects in a distant elsewhere — but of course, the real consequences are rarely that neat. For particularly large-scale projects and products that incorporate AI/ML, the cost of processing power is only a fraction of the environmental impact that is incurred. The sprawling and cascading environmental effects include the carbon emissions and environmental effects incurred from the larger supply and logistic chains that bring these products together, such as hardware and transcontinental infrastructures. These often have very specific requirements, such as the need for vast data centers that can cool off without being too costly, the strategic geographic routes needed for edge computing, the need for materials such as lithium and rare earth metals, and the particular disposal processes of e-waste in the afterlife of the computing industry [2], [18], [21] — all of which contribute to the larger effects of extraction, displacement, and destruction that are almost always felt more acutely by certain communities.

Exporting AI?

Data artefacts are very much deeply entangled with their material basis as a growing body of literature has made abundantly clear. We have gone beyond merely acknowledging the importance of place and have embarked on the difficult project of mapping out exactly the ways that AI/ML systems are tethered to space, time, and matter — as well as its myriad implications. Place matters, including:

Where an AI/ML model is made; who funds it, who made it and who it is made for

What data it relies on, who sorts the data and to which categories, whose expertise is used and whose is ignored

Who has ownership over the data pipelines and computing infrastructure

Which jurisdiction are these models accountable to

What raw materials, resources, and labour are needed for the system to be made and be functional

What are the environmental impacts of the wider supply chain

What imperial/colonial relations and dependencies are reified in the process

It becomes increasingly important then, to converse about ways to better embed geographies in discussions on AI/ML and its governance. As AI systems maintain their abstract, frictionless, and intangible appearances, they manage to squirm out of regulation, scrutiny, criticism. How can we ground AI, cloud computing, platforms and other lofty corporate-derived words into more tangible and physical terms [6], [22]–[24]? If the infrastructures, imperial legacies, and material benefits are all tangible and geographically situated, how can our vocabularies better reflect this?

What exactly are we exporting when we export AI systems?