Ethical AI, Bias Mitigation & Privacy ⚖️

Bias is a systematic error that pushes a model's outputs in one direction for one group. It rarely comes from one villain — it leaks in at several points, and your job is to know all of them.

• Training data: if past hiring favoured one group, the model learns "favour that group" as a rule.
• Sampling: if a group is barely present in the data, the model never learns to serve it well.
• Labels: the "correct answers" themselves may encode human prejudice (who was approved before).
• Proxy variables: a feature like ZIP code or first name can secretly stand in for race or gender.
• Objective: optimising only for accuracy lets the model ignore small groups entirely.

Real systems have caused real harm by missing these:

You can't fix what you don't measure. The simplest fairness metric is demographic parity: the selection rate (the share of a group that gets a positive outcome) should be roughly equal across groups.

Regulators turn that into a number with the 4/5ths rule: divide the lowest group's selection rate by the highest to get the disparate-impact ratio. If it falls below 0.8, that is treated as adverse impact you must investigate.

Parity alone can be misleading, so also check equalised odds: among people who actually deserved a positive outcome, the model's success rate should be the same for every group. The worked example below computes selection rates per group and the disparate-impact ratio from a tiny dataset — read every comment, then run it.

# ============================================
# WORKED EXAMPLE: where does bias hide?
# Pure Python — no libraries needed.
# ============================================

# A loan model already made decisions on 12 applicants.
# Each row: (group, approved?)  approved = 1, denied = 0
applicants = [
    ("A", 1), ("A", 1), ("A", 1), ("A", 0),
    ("A", 1), ("A", 1),                        # Group A: 5 of 6 approved
    ("B", 1), ("B", 0), ("B", 0), ("B", 0),
    ("B", 1), ("B", 0),               
...

If a model denies someone a loan, they deserve to know why. Explainability tools answer that by attributing one prediction to the features that drove it: "+0.30 from income, −0.90 from late payments". That turns a black box into a sentence a human can challenge.

SHAP uses game theory to split a prediction fairly among its features and is consistent across the whole model. LIME builds a quick, simple approximation around a single prediction. The worked example shows the core idea — every feature's contribution is its value times its weight — and points to the real libraries.

# ============================================
# WORKED EXAMPLE: explainability (the SHAP / LIME idea)
# Why did the model deny THIS person? Attribute the score
# to each feature. Pure Python — the real tools just do this
# rigorously across the whole model.
# ============================================

# A simple, fully transparent scoring model.
# Each feature has a weight; score = sum(feature * weight).
weights = {"income": 0.6, "age": -0.2, "late_payments": -0.9}

applicant = {"income": 4,
...

PII (personally identifiable information) is anything that pins data to a real person — name, email, exact address. The first rule is simple: strip direct identifiers before the data reaches the model.

But redaction is not enough — clever attackers can re-identify people from "anonymous" patterns. Differential privacy fixes this by adding calibrated random noise so that adding or removing any single person barely changes the result. The knob is the privacy budget epsilon (ε): lower ε means more privacy and less accuracy. The worked example redacts PII and applies the differential-privacy idea to a salary average.

# ============================================
# WORKED EXAMPLE: privacy — PII and differential privacy
# Pure Python. The real tools (below) automate the maths.
# ============================================
import random
random.seed(0)

# Step 1: never train on raw PII (personally identifiable info).
record = {"name": "Jordan Lee", "email": "jlee@mail.com", "salary": 52000}
# Redact direct identifiers BEFORE the data reaches the model.
safe = {k: v for k, v in record.items() if k not in ("name
...

Accountability means a specific, named human owns the model's outcomes — not "the algorithm". When a decision is wrong, there must be a person to appeal to, a log of what the model did, and a clear path to override it. "The model said so" is never an acceptable answer.

Concretely, an accountable system has:

• An owner: a named team responsible for harms, not just accuracy.
• An audit trail: logged inputs, outputs, and model versions so you can reconstruct any decision.
• A human in the loop: someone who can review and reverse high-stakes outcomes.
• A model card: a short document stating the model's intended use, limits, and known risks.

You also have to think about misuse — harm caused by using the model outside its intended purpose. A face-matcher built for unlocking phones could be repurposed for mass surveillance; a text generator could mass-produce scams or disinformation. Mitigation means restricting access, rate-limiting, watermarking outputs, refusing dangerous requests, and red-teaming the system before release.