Skip to content

Frontier AI as Strategic Infrastructure: Sovereign Governability Under Dependency

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

When personal data enters an artificial-intelligence development lifecycle, deleting the original record may not end the consequences of an unlawful, deceptive, or otherwise prohibited data practice. The data may have informed a model, algorithm, embedding, feature set, evaluation corpus, or other operational artifact. This working paper examines a recurring remedial pattern in Federal Trade Commission enforcement matters: in appropriate cases, the Commission has required deletion or destruction not only of covered source information but also of specified information, work product, models, algorithms, or data products derived from it. The pattern begins earlier than most AI-governance accounts acknowledge. In the 2019 Cambridge Analytica final order, entered after the respondent failed to answer the FTC’s administrative complaint, the Commission required deletion or destruction of covered information and any information or work product, including algorithms or equations, that originated in whole or in part from that covered information. In Everalbum (2021), the Commission used the defined term “Affected Work Product” for models or algorithms developed in whole or in part using covered biometric information. In Kurbo/Weight Watchers (2022), a stipulated order required destruction of affected work product developed in whole or in part using children’s personal information collected through the Kurbo program. In Ring (2023), a federal court order required deletion or destruction of reasonably identifiable affected work product, subject to a sworn certification process where destruction was technically infeasible. In Rite Aid (2024), the FTC paired a five-year facial-recognition-use prohibition with deletion or destruction of covered photos and videos and data, models, or algorithms derived in whole or in part from them, along with third-party notification and deletion-direction obligations. Amazon Alexa (2023) occupies a related but distinct role: it illustrates the enforcement significance of retention, deletion commitments, and restrictions on future use of information subject to deletion directions, rather than serving as a general precedent for deletion of already-trained models. These matters do not establish a universal doctrine of “tainted AI.” They do not hold that every downstream artifact associated with problematic data is automatically unlawful, that every customer of a model vendor inherits liability, or that every deletion request always requires erasure of model parameters. The applicable remedy remains dependent on statutory authority, procedural posture, operative order language, covered data, derivation nexus, technical feasibility, and proportionality. The matters nevertheless reveal a consequential enforcement logic: a firm may not always retain specified informational or algorithmic value created from data it had no right to collect, retain, or use in the relevant manner. This working paper develops that logic into a governance framework for verifiable AI remediation. It proposes a Full-Lineage Remediation Standard, a Training Provenance Record, a derivation-nexus analysis, a material-contribution inquiry for large mixed training corpora, and an evidence hierarchy for deletion, model retirement, retraining, and machine unlearning. It also compares the U.S. remedial pattern with the European Data Protection Board’s Opinion 28/2024 on AI models and personal data, which recognizes that unlawful processing in model development may affect subsequent deployment and that supervisory authorities may impose proportionate corrective measures extending from dataset erasure to retraining or, in appropriate cases, erasure of an AI model. The paper concludes that AI governance must be capable not only of recording what data a system holds, but of evidencing what that data helped build, where the resulting artifacts reside, and what action the organization took when the underlying data practice failed.

View source

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 178 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Conference Open access Dec 2013

Affordable and Energy-Efficient Cloud Computing Clusters: The Bolzano Raspberry Pi Cloud Cluster Experiment

The ongoing work building a Raspberry Pi cluster consisting of 300 nodes is presented, with potential use cases being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.

P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al. · 110 citations · ⚡7
#computer vision Book Open access Mar 2017

On the Unhappiness of Software Developers

The results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains, and 219 factors representing causes of unhappiness while developing software are identified.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 84 citations · ⚡6

Related blog posts

Microsoft Research Blog Oct 12, 2026

Simulating student learning for better AI tutoring

StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring appeared first on Microsoft Research.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.