On a cold January morning in 2020, Robert Williams was standing in his driveway in Detroit when two police cars pulled up. Officers handcuffed him in front of his wife and two young daughters and drove him to a detention facility, where he spent the night in a cell. He had no idea what he was accused of.
The charge was felony armed robbery — a crime that carries years in prison. Williams had never been to the store that was robbed. He had no connection to the incident whatsoever. But a facial recognition system used by the Detroit Police Department had matched his driver's license photo to grainy security footage, and a human analyst had confirmed the match without investigating further.
Williams was released after 30 hours. He was the first known American to be wrongfully arrested based entirely on a facial recognition error. He was not the last. Similar cases followed in New Jersey in 2021 (Michael Oliver, charged with a crime he didn't commit) and in New Orleans in 2023 (Randal Reid, jailed for six days for a theft that occurred in a state he had never visited).
In every case, the process was roughly the same: an AI system flagged a face, a human rubber-stamped the result, and a real person's life was disrupted — sometimes severely — before anyone asked whether the machine had simply been wrong.
Facial recognition AI works by measuring features of your face — the distance between your eyes, the shape of your jaw — and comparing them against a database. It doesn't "see" the way you do. It sees patterns of pixel data and calculates a probability score: this face is X% likely to match that face.
The problem is that these systems were trained mostly on data that skewed heavily toward lighter-skinned faces, especially male ones. A landmark 2018 study by MIT researcher Joy Buolamwini found that some commercial facial recognition systems had error rates as low as 0.8% on lighter-skinned men — but as high as 34.7% on darker-skinned women. That's not a small rounding error. That's one in three faces misidentified.
This means the people most likely to be wrongly accused by facial recognition AI are those who were already underrepresented in the training data. The system didn't "decide" to be biased in any human sense — it learned from biased data, and the bias became baked in.
After Robert Williams was released, Detroit Police admitted that the facial recognition match should never have led to an arrest on its own. Their official policy said AI results were meant to be "investigative leads" — starting points, not conclusions. A human analyst was supposed to verify the result before anyone got arrested.
But here's what actually happened: the human analyst looked at the AI's match, agreed with it, and moved on. The phrase "a human was in the loop" technically described the situation. But in practice, the human deferred to the machine. That's a pattern researchers call automation bias — the tendency to trust automated systems more than our own judgment, especially when we're tired, pressured, or when the machine seems confident.
This creates a real problem. When companies or governments deploy AI in high-stakes situations — criminal justice, hiring, medical diagnosis — they often point to the human in the loop as the safety net. But if that human consistently defers to the AI, the safety net isn't really there. The accountability disappears into a gap between "the machine suggested it" and "a person confirmed it."
If a police analyst confirms an AI match that turns out to be wrong — and someone is wrongly arrested — who is responsible? The company that built the AI? The analyst who agreed with it? The police department that deployed it? The city that permitted it? There is no clean answer here. That's exactly the problem.
Robert Williams didn't just quietly accept what happened to him. With support from the American Civil Liberties Union (ACLU), he sued the City of Detroit in 2021. His case — and the cases that followed — pressured the city to update its facial recognition policies and sparked legislation in multiple states restricting how law enforcement can use the technology.
Joy Buolamwini didn't just publish her research and move on. She founded the Algorithmic Justice League in 2016, a nonprofit that challenges bias in AI systems through research, art, and advocacy. She testified before the U.S. Senate. Her work directly influenced several companies to change their facial recognition products.
Neither of these people had a magic "fix AI" button. What they had was the ability to name what was wrong, document it, and bring it into spaces where decisions get made. That is what standing up looks like in the age of AI — not fighting the machine, but forcing the humans behind it to be accountable.
Most people who read a headline about a "facial recognition error" assume it was a rare malfunction — a one-time glitch. You now know it's a structural problem rooted in biased training data, compounded by automation bias, and made worse by unclear accountability. That's a completely different situation. And knowing the difference changes how you evaluate every AI deployment you'll encounter.
A city is considering expanding its facial recognition program from law enforcement to school security — scanning students' faces at building entrances. You've been asked to assess the risks before the city council votes. Your AI partner has been briefed on the technology and the documented cases of error.
This isn't a research exercise — you need to take a position and defend it. Your AI partner will push back on weak arguments.
Starting in 2014, Amazon built a machine learning tool designed to automate the hiring process. Engineers fed it ten years of résumés that had been submitted to Amazon — and the job titles those applicants ended up with. The idea was elegant: teach the machine what a successful Amazon employee looks like, then use it to sort future applications.
By 2015, the team noticed something alarming. The system was systematically downgrading résumés that contained the word "women's" — as in, "women's chess club" or "women's college." It was also penalizing graduates of all-women's colleges. The system had noticed that most successful Amazon engineers over the past decade were men, and had learned — on its own, without being told to — to treat maleness as a positive signal and femaleness as a negative one.
Engineers tried to fix it. They removed the specific phrases the model had flagged. But they couldn't guarantee the model hadn't found other proxies for gender — writing style, extracurricular activities, anything that might correlate with being a woman. By 2018, Amazon shut the project down entirely. They later confirmed the tool had never been used to make actual hiring decisions. But the story became one of the most-cited examples in AI ethics because of what it reveals: a system can learn to discriminate without anyone programming it to.
The Amazon engineers didn't build a sexist AI. They built a system that learned from historical data — and that data reflected a decade of hiring decisions made in an industry where women were significantly underrepresented in technical roles. The AI treated "what worked before" as "what should work now." It replicated the past.
This is sometimes called historical bias — when the unfairness of past decisions gets encoded into the patterns an AI learns, and then projected forward. The math is entirely neutral. The outcome is not.
What makes this especially difficult to challenge is that the discrimination is invisible by design. When a human hiring manager discriminates, they leave a paper trail — emails, interview notes, someone who might testify. When an algorithm discriminates, it produces a score. The score looks objective. Most of the time, the rejected candidate never even knows they were screened out by a machine, let alone why.
Amazon is not alone. A 2019 investigation by ProPublica and The Markup documented AI screening tools being used by hundreds of major employers. Studies showed that AI résumé screeners commonly favored applicants with names that sounded white and male, even when all other qualifications were identical. The 2021 HireVue facial analysis controversy revealed that some AI hiring tools were analyzing candidates' facial expressions during video interviews and generating personality scores — with no publicly available evidence that those scores predicted job performance.
This matters at an institutional level: by 2022, an estimated 99% of Fortune 500 companies were using some form of automated screening in their hiring process. The decision about whether you even get a human to look at your application is increasingly made by a system you never see and can't appeal to.
In 2023, the U.S. Equal Employment Opportunity Commission (EEOC) issued guidance confirming that employment discrimination through AI tools is still illegal under existing civil rights law — meaning companies can be sued even if "the algorithm did it." The European Union's AI Act, passed in 2024, classifies AI hiring tools as "high-risk systems" requiring mandatory transparency and human oversight. These are real policy changes, driven directly by documented cases of AI bias.
If a company uses an AI hiring tool that turns out to discriminate, but the company genuinely didn't know it would — and the tool was built by a third-party vendor — who bears responsibility? The company that used it? The vendor that built it? The engineers who trained it on biased data? And what about the candidates who were rejected and never found out?
You can't demand access to a company's proprietary hiring algorithm. But researchers, journalists, and advocates have developed tools for pressuring AI systems into revealing their biases — even without the source code.
One method is audit testing — sending identical applications with different names or demographic signals and comparing outcomes. This is the same method civil rights organizations used to document housing discrimination in the 1960s. It still works. In 2021, researchers at MIT used audit testing to show that AI-powered loan pricing tools charged Black applicants higher rates than white applicants with identical credit profiles.
Another tool is public disclosure: in 2021, New York City passed Local Law 144, which requires employers using AI hiring tools to commission annual independent bias audits and publish the results. It was the first law of its kind in the United States. It exists because advocates documented the problem and showed up at city council hearings.
You can't fix what's invisible. But once you know where to look, you can force the light on.
Most people think discrimination requires a discriminatory intent — someone who wants to be unfair. What you now know is that AI systems can produce discriminatory outcomes through pure pattern-matching on historical data, with no one intending any harm. That distinction matters enormously in law, in policy, and in how you think about fairness in any system that uses AI to make decisions about people.
A local university is using an AI tool to screen applications for its summer scholarship program. Preliminary data suggests students from certain zip codes are being accepted at far lower rates — but the university says the AI only considers grades and test scores, not location. You need to figure out whether that claim holds up and what evidence you'd need to make a case.
In February 2023, Mark Walters, a radio host in Georgia, discovered that the AI chatbot ChatGPT had described him — in a legal summary generated for a journalist — as having embezzled funds from a Second Amendment organization where he served as treasurer. There was one problem: none of it was true. Walters had never been accused of embezzlement. The organization mentioned didn't match any he was associated with. The case number in the summary was fake. The court where the supposed lawsuit was filed didn't exist.
ChatGPT had invented the entire thing. Not maliciously — the model doesn't have intentions — but confidently, fluently, and in exactly the format of a real legal document. Walters sued OpenAI in June 2023 in what became one of the first defamation lawsuits against an AI company in the United States.
His case was not unique. A law professor named Jonathan Turley found that ChatGPT had generated a fake sexual harassment allegation against him, complete with a fabricated Washington Post article as a source. Brian Hood, the mayor of Hepburn Shire in Australia, threatened to sue OpenAI after ChatGPT falsely described him as a convicted criminal — he had actually been a whistleblower, not a criminal. These events all occurred within a six-month window in early 2023 as large language models were first deployed at scale.
The AI industry calls this problem hallucination — when a language model generates text that sounds accurate but is factually wrong. The word is everywhere. It's also, in a subtle way, misleading.
"Hallucination" makes it sound like the AI is confused, or like it briefly lost its grip on reality — the way a person might after not sleeping for 40 hours. But that framing implies a baseline state of being "grounded in reality" that language models don't have. A large language model doesn't know facts. It generates text that statistically resembles text it was trained on. When it produces something factually accurate, it's because accuracy correlates with how humans write. When it produces something false, it's because the false statement also fits the statistical patterns of the training data.
The more accurate framing is confabulation — generating plausible-sounding content to fill a gap, without any mechanism for checking whether it's true. It's not a bug in an otherwise reliable system. It's a structural feature of how these systems work.
Defamation — the legal term for a false statement of fact that damages someone's reputation — has existed as long as publishing has. What changes with AI is scale and searchability. A false statement in a small-town newspaper might reach a few thousand readers. A false statement in a widely-used AI chatbot gets reproduced every time someone asks the right question — potentially millions of times, in different conversations, with no single place to issue a correction.
The legal situation is unsettled. U.S. defamation law requires showing that the defendant acted with at least negligence — and it's still unclear how intent-based defamation frameworks apply to systems that have no intent at all. The Walters lawsuit was dismissed in 2024 on technical grounds, but similar cases continue to work through courts in the U.S., UK, and EU. Meanwhile, the EU's AI Liability Directive, proposed in 2022 and still advancing in 2024, would make it easier for people harmed by AI to access evidence and pursue legal claims.
Practically, victims of AI defamation currently have limited tools. They can contact the AI company directly — OpenAI and Google have processes for reporting false information, though correction is not guaranteed. They can publish corrections and document the false content carefully. And they can bring legal action, though courts are still figuring out the rules.
AI companies argue they can't manually review everything their models generate — it's simply too much content. But if a company deploys a system that regularly generates false statements about real, named people, and those false statements are presented without any disclaimer, is the company ethically responsible for the harm? Does it matter if they "didn't know" any specific statement was false?
If you encounter an AI generating false information about a person — yourself or someone else — the most important thing is to document it precisely. Screenshot the output. Record the exact prompt you used. Note the date, the platform, and the model version if available. This creates a record that doesn't depend on the AI maintaining that specific output (since model outputs can change over time).
Most major AI platforms have a feedback or reporting mechanism. These reports do affect model behavior over time — not for that individual conversation, but as part of the ongoing process of refining outputs. Reporting is not futile; it is a form of participation in how these systems evolve.
Beyond individual action: organizations like the Electronic Frontier Foundation (EFF), the Center for Democracy and Technology (CDT), and the AI Now Institute specifically track and respond to cases of AI harm to individuals. Connecting documented cases to organizations that can amplify them is one of the most effective ways to convert individual harm into systemic pressure.
When someone tells you an AI is "just making stuff up" about a person, they often mean it as a minor complaint about a quirky technology. You now understand why it's a serious issue with real legal, reputational, and safety stakes — and why the word "hallucination" obscures more than it explains. You also know what to do about it. Most people don't.
A student at your school tells you that a popular AI chatbot is describing her older sister — a local community organizer — as having a criminal record for fraud. The sister has never been charged with any crime. The student wants to know what to do. You've been brought in as a digital rights advocate to advise her.
In 2023, a group of high school students at Lowell High School in San Francisco noticed something troubling in how an AI tutoring tool recommended college prep resources. Students from lower-income families who used the tool were being steered toward community college pathways and vocational programs, while students with similar grades but markers of higher income were being recommended four-year university preparation resources. No one had programmed this difference in. The AI had inferred economic status from patterns in how students wrote their prompts and what devices they were using.
The students didn't accept it quietly. They documented specific cases — anonymized but detailed — and brought them to their school district's technology committee. They wrote a one-page report explaining what they had observed and asked three specific questions: Who selected this tool? What bias testing was done before deployment? Who is responsible if the tool disadvantages students?
The district paused use of the specific tool for review. The vendor was asked to provide its bias audit documentation. The students had not written a single line of code. They had not gone to court. They had done something simpler and more powerful: they had named the problem precisely, put it in front of the people with authority over it, and demanded a specific response.
What made the Lowell students effective wasn't anger or virality — it was precision. Vague complaints about AI ("this tool is unfair") get no traction. Specific, documented observations ("this tool recommended different outcomes for students with comparable grades, and here are four examples") are much harder to dismiss.
Effective pushback against AI errors tends to have these components:
1. Specific documentation. Not "the AI said something wrong" but "on this date, using this prompt, this platform generated this specific output." Screenshots, quotes, timestamps.
2. A named harm. Not "this might be a problem" but "this caused or could cause X specific consequence to Y specific type of person." Harms that can be described concretely are much easier to respond to than harms that remain abstract.
3. A clear audience. Who has the power to act on this? A school district technology committee. A company's trust and safety team. A journalist covering AI policy. A city council member proposing AI legislation. Pushback aimed at no one in particular usually stays that way.
4. A specific ask. Not "do something about this" but "pause this deployment pending review" or "release your bias audit results" or "add a disclaimer to outputs about real people." Specific asks create accountability — a person either did the thing or they didn't.
There is a specific credibility that comes with being a user of a tool who was directly affected by it — and there is a specific credibility that comes with being young in a conversation about technology that will shape your entire adult life. Neither of those is a small thing.
In 2022, a 16-year-old student in the UK named Shreya Agarwal became one of the named complainants in a legal challenge to an AI grading system used by the UK government during the COVID-19 pandemic. That system — called the A-level algorithm — had assigned grades to students based partly on their schools' historical performance, disadvantaging students at lower-performing schools who were individually capable of exceeding their school's average. After widespread protest by students and parents, the UK government reversed the grades of approximately 280,000 students. An AI grading decision affecting hundreds of thousands of young people was reversed, in part because students said clearly and publicly: this is wrong, this is why, and this is what we need changed.
In 2021, the Dutch government's child welfare fraud detection algorithm — known as SyRI — was ruled illegal after legal challenges partly driven by affected families who documented its discriminatory targeting of lower-income and immigrant households. The system had flagged families for potential benefits fraud based on patterns that disproportionately affected certain ethnicities. The Dutch court ruled it violated human rights law. That ruling set a precedent that influenced AI regulation debates across Europe.
When you push back against a biased AI system and it gets changed or removed, the new system might have different flaws you don't know about yet. Does that make pushback pointless — or does getting the process right matter even if the outcome is imperfect? At what point is "this AI causes less harm than before" good enough?
This module has been about specific documented cases where AI systems caused real harm, and specific real people who did something about it. None of them had magical credentials. What they had was:
The ability to notice that something was wrong. The discipline to document it precisely rather than just getting angry. The clarity to name the harm in terms others could understand. The knowledge of who to take it to. And the persistence to follow through.
Those are not technical skills. They are not adult-only skills. You have been building them throughout this course — in every lesson where you analyzed a case, in every lab where you were asked to take a position and defend it, in every quiz where you had to apply a concept to a new situation rather than just remember a definition.
The AI systems being built and deployed right now will be part of your world for decades. The decisions being made in 2024 and 2025 about how they work, who they serve, and who holds them accountable — those decisions are still being contested. That means there is still time to influence them. The question is whether people who understand the stakes show up.
Now you understand the stakes.
Most adults assume that challenging AI systems requires technical expertise, legal resources, or institutional power. You now know that the most effective challenges have consistently come from people who could clearly describe a specific harm, name who was responsible for it, and make a specific ask. You are capable of doing all three. That is not a small thing.
Your school district is considering purchasing an AI-powered student behavior monitoring system. The system would analyze students' writing, browsing patterns on school devices, and even keystrokes to flag potential mental health risks or disciplinary issues — and would send alerts to teachers and counselors without students' knowledge.
You've been asked to present a one-minute statement to the school board before the vote. Your AI partner is a policy advisor who will help you sharpen your argument — but they'll also push back hard if your reasoning has gaps.