AI system transparency registers
A public, machine-readable account of which AI system powers each government service, delivered to the user at the point of use rather than left in a register. A person challenging an outcome can name the specific system that produced it, the fact every accountability process needs first.
The impact of agents
A user has no way to establish which system is handling an interaction, who built it, where it is hosted, or what data it was trained on, and neither does the agent acting on their behalf. That gap widens as more government services come to run on AI. Without that account, a decision cannot be checked against who is accountable for it, and the jurisdiction the system answers to stays invisible at the moment it matters.
The system behind a service has to be identifiable to a user or an agent at the point of use, not only to those who go looking in a register.
What must be verified
Government must keep a verifiable, machine-readable account of which AI system powers each service, recording its purpose, training data, underlying technology, and risk controls. A user or an agent can then confirm what is handling an interaction and who answers for it. A record that exists only on a register a user never reaches does not meet that requirement at the point of use.
Protecting access
Register-only disclosure excludes users who don't know a register exists, or who lack the time or technical confidence to read one. They act without knowing what system handled them. A disclosure repeated on every interaction excludes the same people differently: fatigue trains everyone to click past it.
Keeping the path open
- Bring the register's facts into a glanceable, contextual indicator at the point of use: 'powered by X, hosted in Y, registered under Z'.
- Write it in plain language, and trigger fuller disclosure only where the jurisdiction genuinely changes the user's position.
- Make the indicator reachable by keyboard alone and read out by a screen reader, with the model, jurisdiction, and register status announced as text rather than implied by an icon.
Response surface
At the point of use, one line names the system, where it is hosted, and the public register entry that describes it.
The chip appears wherever the system operates rather than on a separate transparency page, and it resolves to the register record instead of restating it, so the disclosure cannot drift from the entry it points at.
Maturity
- Established
For government AI registers, operating in the UK and Netherlands.
- Emerging Headline
For mandatory disclosure obligations under the EU AI Act, in force from August 2026.
- Frontier
For real-time, contextual AI system disclosure at the point of user interaction.
Precedents
The UK Algorithmic Transparency Recording Standard. The UK mandated ATRS reporting across all government departments, and the scope policy extended it to arm's-length bodies providing public or frontline services or routinely interacting with the general public. What is caught are tools that significantly influence a decision with public effect, or interact with the public directly, and the standard requires disclosure of purpose, training data, underlying technology, and risk-management strategies. More than 125 records have been published.
The Netherlands Algorithm Register. The Netherlands launched a public algorithm register inviting government bodies to publish the algorithms they use rather than obliging them to, and 1,520 are listed. The Dutch Data Protection Authority found that more than half of municipalities and over three-quarters of independent administrative bodies had registered nothing, that only 5 percent of registered algorithms carried a fundamental-rights assessment, and called for registration to be made mandatory. The distance between what is listed and what is in use is the measure of a voluntary register.
EU AI Act Article 50, transparency obligations. Providers of AI systems intended to interact directly with natural persons must ensure those persons are informed they are interacting with an AI system, and providers of systems generating synthetic content must mark outputs in a machine-readable format. Non-compliance draws administrative fines of up to EUR 15 million or 3 percent of worldwide annual turnover. The higher tier applies to prohibited practices, and not to transparency breaches.
EU AI Act Article 13, information for deployers. Providers of high-risk AI systems must deliver instructions that are 'concise, complete, correct and clear', covering intended purpose, accuracy metrics, and details of training and validation data. The duty creates an information chain running provider to deployer to user.
What carries over to agent use
The ATRS and Dutch register models provide the structural template for AI system disclosure. However, they are currently registry-based, published on a government website for those who seek them out. In an agent-mediated interaction, the disclosure needs to be surfaced at point of use, not discovered in a register after the fact.
The design challenge is adapting registry information into a glanceable, contextual indicator. The Article 50 obligation provides the legal mandate and the registries provide the data; the part still to be built is the interaction that brings that data to the user at the point of use.
A government can already disclose which model powers a function at the level of a procurement notice, as France did in notifying its framework agreement with Mistral AI. What does not follow from that is the disclosure a user meets: a procurement notice is read by those who go looking for it, which is the same limitation the registers carry.
Where things go wrong
The failure mode is an algorithm whose purpose, training data, and risk controls are never exposed, so a flawed design cannot be contested before it scales. A mandatory, public transparency register makes it contestable in advance. A register entry can also be filed and still say nothing useful: a generic purpose statement and stock risk-control language satisfy the mandate without naming the training data or the specific risk the record exists to expose. That entry passes a check for whether the field was completed, not a check for whether the system can be contested.
Sources
12 references
The instrument, the operating deployment, or the official record itself.
- GOV.UK — Algorithmic Transparency Recording Standard Hub
- GOV.UK — ATRS Mandatory Scope and Exemptions Policy
- Data in Government blog — Making ATRS mandatory
- Algorithm Register of the Dutch government
- Dutch government — 1000th algorithm published in the Algorithm Register
- Autoriteit Persoonsgegevens — Algorithm registration in the Netherlands needs improvement
- EU Digital Strategy — Draft guidelines on transparency obligations
- EUR-Lex — Regulation (EU) 2024/1689 (AI Act), Article 13
- Ministry of Armed Forces notifies a framework agreement to Mistral AI — communiqué
Writing about the subject rather than the framework itself, including vendor commentary.