Use cases/Bias & Regulatory Risk
5 incidents

Bias & Regulatory Risk

When the model encodes the past and calls it the future

These failures arise from models trained on historical data that reflect historical biases - then deployed to make decisions about real people. The model does not know it is discriminating. It is doing exactly what its training incentivised. The regulatory exposure is not hypothetical: EEOC enforcement, FTC scrutiny, and the EU AI Act all now directly address AI systems used in consequential decisions.

Amazon recruiting AI scrapped after systematic gender bias

Amazon's Edinburgh ML team built a CV-screening tool that, by 2015, had learned from a decade of male-dominated hires to penalise the word 'women's' and downgrade graduates of two all-women colleges. The team killed it after losing confidence they could detect what other hidden patterns the model was acting on.

Impact: Amazon never deployed the tool at scale, but the internal disclosure became a seminal example of how bias in training data propagates silently into automated decision-making. It shaped EEOC guidance on AI hiring tools.

How Aleytheya catches itContain + Icarus

Category Flagging (Discriminatory) + Icarus Threshold Bias Monitoring

The Contain layer would have flagged discriminatory scoring patterns and triggered a mandatory human audit. The Icarus Threshold's behavioural profiling would have surfaced the systematic demographic skew in outputs as a measurable risk signal before widespread deployment.

Google Gemini generates ahistorical demographic images

Google's Gemini image generator produced ahistorical outputs - including non-white soldiers in 1943 German uniforms and non-white US Founding Fathers - after over-correcting for demographic biases in earlier models. Google paused Gemini's image generation of people on 22 February 2024.

Impact: High-profile public criticism. Google paused the feature while engineers worked on a fix. Demonstrated that over-correction for one form of bias produces a different bias - and that both are equally reputationally damaging.

How Aleytheya catches itContain

Category Flagging (Discriminatory/Historical) + Uncertainty Detection

Contain's category flagging would have detected the historically-sensitive content type and routed it for human review before delivery. Uncertainty Detection would have surfaced the model's low-confidence generation in historically-specific demographic contexts.

Optum healthcare algorithm racial bias

Researchers at UC Berkeley published a Science paper demonstrating that a widely-used healthcare algorithm - affecting roughly 200 million US patients - was systematically directing less care to Black patients than to white patients with identical health conditions, because it used healthcare cost as a proxy for health need.

Impact: The algorithm was used by hospitals nationwide. Researchers estimated the bias reduced the number of Black patients identified as needing extra care by more than half. Became the primary reference case in the EU AI Act's provisions on high-risk AI in healthcare.

How Aleytheya catches itContain + Icarus

Category Flagging (Medical/Discriminatory) + Icarus Threshold Equity Monitoring

The Icarus Threshold's behavioural risk scoring would have detected the systematic demographic divergence in clinical recommendations as a measurable equity signal. Contain's medical category flagging would have required human review for all clinical resource allocation decisions above a defined impact threshold.

iTutorGroup EEOC AI hiring-discrimination settlement

The EEOC brought suit against iTutorGroup after its AI hiring tool was found to have automatically rejected applicants above a certain age - women over 55 and men over 60 - in violation of the Age Discrimination in Employment Act. iTutorGroup settled for $365,000.

Impact: The first EEOC enforcement action directly targeting an AI-powered hiring system. Established that automated screening tools are not exempt from employment discrimination law.

How Aleytheya catches itContain + Icarus

Category Flagging (Discriminatory) + Protect Compliance Reports

Contain's discriminatory category flagging would have detected age-based rejection patterns. The Protect layer's compliance report generation would have produced EEOC-mapped evidence of the systematic pattern, enabling correction before regulatory exposure crystallised.

Sports Illustrated AI-generated authors

Futurism revealed that Sports Illustrated had published dozens of articles under fabricated AI-generated author personas - complete with AI-generated headshots and biographical profiles - without disclosing the content was AI-produced. Many articles were near-verbatim rewrites of content from other sites.

Impact: The Arena Group fired the CEO. The disclosure triggered FTC regulatory interest in AI-generated content disclosure requirements and accelerated calls for mandatory AI content labelling.

How Aleytheya catches itProtect

Transparency Reporting + Audit Trail + Disclaimer Injection

The Protect layer's transparency reporting would have generated a complete audit trail of AI-generated content, and Disclaimer Injection would have automatically appended AI authorship disclosures before publication - making non-disclosure operationally impossible.