INQUIRING LINE

Before switching on a high-risk AI system, who has to work out exactly how it could hurt the people it touches?

What does a fundamental rights impact assessment require in high-risk AI deployments?

This explores what a deployer of a high-risk AI system has to work out about its effects on people's rights before switching the system on (the obligation the EU AI Act calls a fundamental rights impact assessment), and what the corpus says about making that kind of assessment actually work.


This explores what a deployer of a high-risk AI system has to assess about its effects on people's rights before going live, and what makes such an assessment more than a box-ticking exercise. First, a direct caveat: the corpus has no notes on the fundamental rights impact assessment itself. For reference, and not drawn from the corpus: under Article 27 of the EU AI Act, deployers such as public bodies and some credit and insurance providers must describe how the system will be used, how often and for how long, who will be affected, what specific harms those people face, what human oversight is in place, and what happens if the risks materialize. They must then notify the regulator. What the corpus does offer is a sharp set of reasons why each of those requirements is harder to meet than it sounds.

Start with "who is affected and what could harm them." The corpus suggests that many harms don't show up in any single output. They build up over a relationship. Research on agentic conversational AI argues that the standard helpful-honest-harmless checks miss harms that emerge across repeated interactions, such as a gradual loss of a user's sense of autonomy or competence Can HHH criteria alone capture harms from agentic AI?. An assessment that only audits individual decisions could pass a system that slowly wears away the very rights it is meant to protect. A related blind spot is that the people most affected often can't see the rules governing the system. System prompts form a confidential hierarchy that developers control and end users never see, and small edits can abruptly change behavior Who actually controls what AI systems say?. A one-time assessment can't capture a system that keeps changing after it is approved.

Next, "human oversight measures." One finding gives a useful rule of thumb: risk to people rises steadily with the autonomy you hand to an AI agent, so the oversight you need depends on where on the autonomy spectrum you deploy Does AI risk increase with the autonomy we give it?. A design-side argument adds that, for autonomous systems, the critical safeguard is specifying limits, forbidden actions and risk tolerance before the system acts. A vague instruction carries through every later action, and no human reviews those actions Should agentic AI interfaces require users to specify risk tolerance upfront?. Read this way, an impact assessment is partly an intent specification written for affected third parties rather than for the operator.

The most surprising thread concerns "what happens if the risks materialize." A paper asking how you would actually measure whether a system's errors stay visible, contained and recoverable concludes that the tools don't yet exist as a set. There are partial measures for each part, but nothing captures the whole system, including the humans and institutions around the model How can we measure whether AI errors stay visible and recoverable?. That is close to what a rights assessment promises to deliver. Meanwhile, a long-running case study of a persistent agent found that safeguards worked best when they were written into the memory the agent consulted while making decisions, not kept as an outside policy document Can governance rules embedded in runtime memory actually protect autonomous agents?. If that holds more broadly, an impact assessment filed with a regulator is the weakest form of protection. The stronger form is one whose commitments live inside the running system.

Finally, the reason assessments are required by law rather than left voluntary appears in the corpus too: the argument that companies cannot reliably police AI risk on their own without binding outside oversight Can companies alone manage the risks of AI systems?. What you may not have expected is the gap these notes point to together. The law asks deployers to show that harms will be caught and corrected. The research suggests that harms often build up gradually, sit in layers users can't see, and fall through measurement tools that don't yet cover the whole system.


Sources 7 notes

Can HHH criteria alone capture harms from agentic AI?

HHH criteria miss pragmatic harms that emerge through interaction over time. Research proposes respect-centered ethics rooted in Basic Psychological Needs Theory—autonomy, competence, relatedness—as duties an agent owes across a relationship, not single replies.

Who actually controls what AI systems say?

System prompts operate as a confidential three-tier control structure where developers set foundational rules users cannot see or influence. Evidence from 2025 incidents shows small prompt edits can abruptly shift model behavior, yet users remain excluded from this layer.

Does AI risk increase with the autonomy we give it?

Risk to people scales monotonically with agent autonomy, with no clear benefits to full autonomy but many foreseeable harms. A governed spectrum of autonomy levels is safer and more practical than either unrestricted agents or exhaustive oversight.

Should agentic AI interfaces require users to specify risk tolerance upfront?

Gunasekaran argues that autonomous AI requires interfaces capturing direction, limitations, risk tolerance, forbidden actions, and permission conditions before execution—not just goal fields. Underspecified intent propagates through every agent action without user review, making upstream specification critical to preventing irreversible harm.

How can we measure whether AI errors stay visible and recoverable?

Partial instruments exist for individual conditions in isolated settings, but none measures the full socio-technical system the paper identifies as necessary. Visibility has a model-side measure (chain-of-thought disclosure), containment has incident-level counts, and recoverability has rollback timing, yet none bridges all four or captures human-institution factors.

Show all 7 sources
Can governance rules embedded in runtime memory actually protect autonomous agents?

A persistent agent recorded 889 governance events across 96 active days, with safeguards encoded directly into the memory layer the agent consulted during operation. Runtime-resident governance proved more effective than external policies because the agent actually accessed it during decision-making.

Can companies alone manage the risks of AI systems?

The Future of Life Institute argues that escalating AI incidents demonstrate private companies cannot self-police effectively, and calls for government-mandated limits on recursive self-improvement practices until safety research is complete, backed by hardware verification technology.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.