AI Threat · Module 3 · Society and Truth

Discrimination at Scale: Bias in Automated Judgement

The lesson follows discrimination through the lifecycle of a system that judges people. Participants learn the five points where bias enters, why it scales and confirms itself, three documented cases with three different mechanisms, the families of fairness metrics and why they cannot all hold at once, and what the AI Act and equality law expect as evidence. They configure a disparate-impact test as a release gate.

Lesson 12 of 35Chapter 1290 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Threat / Module 3 / Chapter 12

Learning objectives

After the lesson the participant can:

Key concepts

Target label
The measurable stand-in a model learns in place of the quantity of interest, such as past health spending for health need. The model inherits every way in which the stand-in differs between groups.
Proxy
A feature such as postcode, first language or length of residence record that correlates with a protected characteristic. Removing the characteristic does not remove its influence if a proxy helps the prediction.
Feedback loop
A model's outputs become its future labels, so its selections confirm themselves, as with patrols sent where more crime is recorded. Article 10 of the AI Act names outputs that influence inputs for future operations.
Disparate-impact ratio
The rate of an outcome for one group divided by the rate for the most favoured group. European law has no fixed threshold; the ratio is a screening signal, not a verdict.
Test enclave
A separate, access-controlled environment where protected attributes are joined for bias detection under the safeguards of Article 10(5), instead of keeping them in the production feature store.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Match

Fairness metrics

Match each metric or rule to what it asks or measures, as the chapter defines it.

Interactive exercise 2 · Scenario

The gate blocks a release

Apply the disparate-impact gate in Nordvik Region's release pipeline.

Teaching plan

15 minThe teacher walks through Table 12.1 and the five points of entry, then why one model applying one pattern to every case is both more damaging and more detectable.
15 minParticipants analyse Gender Shades, the cost-proxy study and the nationality risk factor, naming the mechanism in each and who found the bias.
15 minExplain the three families of metrics and why calibration and equal error rates cannot in general both hold; participants choose and justify metrics for benefits triage and for a verification queue.
35 minExercise in pairs: write a disparate-impact test configuration for a release pipeline modelled on DIT-NR-CR-01, including proxy check, intersections and reporting.
10 minStage the debate on whether measurability makes automated judgement easier to correct, and review the verdict that unaccountability is a property of institutions.

Discussion

  1. In the health-risk case the model was accurate by its own measure. What review, by whom and at what stage, would have caught the choice of what to predict?
  2. In the recidivism dispute both sides were right about what they measured. How should an organisation record and defend its choice of fairness metric when no choice satisfies everyone?
  3. The case for calm says auditability is an advantage of automated judgement; both sides add that it is so only if someone actually audits. Who audits in your organisation, with what access?

Written exercise

Exercise · 35 minutes

A disparate-impact gate for a release pipeline

For a model that ranks or scores people in your organisation, or for Hansa Mutual's underwriting-support model in one market, write a disparate-impact test configuration. State when the test runs. List the protected attributes, where they are sourced and under which safeguards, the intersections to test and the minimum group size. Choose at least one outcome metric and one error metric, each with a blocking threshold and a written reason why that error matters most in this use. Add a proxy check with the action required for a flagged feature. State what happens on a block, who is notified, where a summary is published and how the same metrics are monitored on decided cases.

Deliverable: A test configuration with triggers, attributes and intersections, two or more metrics with thresholds and reasons, proxy check, block action and monitoring.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. What did the Gender Shades evaluation show about testing commercial facial-analysis services?

    Show the answer

    C. Aggregate accuracy hid the disparity, which was largest at the intersection of darker skin and female gender
    The error rate for darker-skinned women reached about a third for the worst service against below one per cent for lighter-skinned men; a test by gender or skin type alone would have understated it.

  2. Where did the discrimination lie in the health-risk algorithm studied by Obermeyer and colleagues?

    Show the answer

    B. In the choice of what to predict: cost as a stand-in for need
    Less money was spent on Black patients with the same need, so predicting cost underestimated their needs. Changing the label to combine cost with direct health measures substantially reduced the bias.

  3. In the worked example DIT-NR-CR-01, what does a breach of a threshold mean?

    Show the answer

    D. It does not prove discrimination but stops the release until people have looked at why
    The thresholds are starting points, not legal standards. The gate blocks promotion and notifies the head of the benefits unit, the AI governance lead and the data protection officer.