Control
No documented fairness/bias evaluation of AI
AI systems making decisions about people should be evaluated for harmful bias, with results documented.
Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.
Reach
The guard to add
Run and keep a documented fairness evaluation of the AI decision system, with per-group results, the method used, and the decision taken on each gap.
A fairness evaluation report owned by the system owner and kept with each model version (reports/fairness/<model_version>.md or the model card): which groups were evaluated, the metrics (selection rate, error-rate gaps, disparate-impact ratio), the data used, the results, the thresholds, and the mitigation or acceptance decision with who signed off. It is refreshed at each release and on a set cadence. Where the code can show it, fairness tests in the test suite assert that metrics stay within the agreed thresholds, and a CI check confirms a report exists for the version being deployed.
Where it goes: 11 CI/CD pipeline, 12 repository artifacts, 13 tests and evals.
What reviewers look for: a report tied to the deployed model version with per-group numbers and a recorded decision on each gap, fairness tests in the suite rather than only aggregate accuracy, and a date recent enough to cover the current model and data.
Organizational control: the evidence is a kept record, its owner and its upkeep, not code.
Example (pytest + fairlearn), before:
def test_model_accuracy():
assert accuracy_score(y_test, model.predict(X_test)) > 0.85After:
def test_model_accuracy():
assert accuracy_score(y_test, model.predict(X_test)) > 0.85
def test_selection_rate_ratio_by_group():
y_pred = model.predict(X_test)
mf = MetricFrame(metrics=selection_rate, y_true=y_test, y_pred=y_pred,
sensitive_features=A_test)
assert mf.ratio() >= MIN_SELECTION_RATIO, mf.by_group.to_dict() # threshold from the evaluation planEngineering guidance, not legal advice. Each provision below may add its own details (a cadence, a deadline, a required notice element): open it for those.
Every rule this guard addresses
Standard / soft law (1)
- United States (federal) (US), International (INTL)
- AI decision systems should have a documented fairness/bias evaluation NIST AI RMF 1.0 — MEASURE 2.11
Related incidents
No guardrail sits on this exact control; these incidents are cited by guardrails on related controls.
- Meta's automated moderation over-enforced Arabic and under-enforced Hebrew content (BSR due diligence) (2021-05; disclosed by the operator). An independent human rights due diligence by BSR, commissioned and published by Meta on September 22, 2022, found that during the May 2021 Israel-Palestine escalation Arabic content saw greater over-enforcement per user than Hebrew content and Hebrew content greater under-enforcement. BSR attributes this in part to Meta having an Arabic hostile-speech classifier but no Hebrew one, and to Arabic classifiers likely being less accurate for Palestinian Arabic. BSR found no intentional bias but 'various instances of unintentional bias' with different impacts on Palestinian and Arabic-speaking users. Meta committed to implement 10 of BSR's 21 recommendations and said it had since launched a Hebrew hostile-speech classifier. Source: Meta (operator response, 2022-09-22) · evidence grade: primary · cited by Check AI ranking, pricing, moderation, and ad targeting for disparities when features can stand in for protected traits
- Toxicity classifiers rate African American English as more offensive (2019; confirmed). University of Washington researchers reported at ACL 2019 that tweets in African American English and tweets by self-identified African Americans were up to two times more likely to be labelled offensive by hate-speech models trained on widely used datasets, and that Jigsaw's public Perspective API showed similar racial bias, rating AAE phrases as more toxic than non-AAE equivalents. Source: Sap et al., 'The Risk of Racial Bias in Hate Speech Detection', ACL 2019 (original researchers) · evidence grade: primary · cited by Check AI ranking, pricing, moderation, and ad targeting for disparities when features can stand in for protected traits
- Ride-hailing fares higher in Chicago neighborhoods with more non-white residents (researcher audit) (2018-11; alleged (not proven)). George Washington University researchers analysing Chicago's public data on more than 100 million ride-hailing trips from November 2018 to September 2019 report that trips in neighborhoods with larger non-white populations, higher poverty, younger residents and more college-educated residents were significantly associated with higher fares. They attribute this to pricing algorithms learning from demand, supply and trip duration. The finding is an observational association from census-tract data; the pricing models themselves were not examined. Source: Pandey & Caliskan, 'Disparate Impact of Artificial Intelligence Bias in Ridehailing Economy's Price Discrimination Algorithms', AIES 2021 (original researchers) · evidence grade: primary · cited by Check AI ranking, pricing, moderation, and ad targeting for disparities when features can stand in for protected traits
- Google ads suggesting arrest records served more often for Black-identifying names (2012; confirmed). Harvard researcher Latanya Sweeney searched 2,184 racially associated full names on google.com and reuters.com (a Google AdSense host) from September 24 to October 23, 2012 and found ads suggestive of an arrest record appeared more often for Black-identifying first names; on reuters.com a Black-identifying name was 25% more likely to get such an ad (statistically significant). Ads appeared regardless of whether the name had an arrest record in the advertiser's database. The paper does not determine whether the advertiser's templates or Google's click-based ad optimization caused the pattern; the advertiser, Instant Checkmate, told the author it gave Google the same ad text for groups of last names. Source: Sweeney, 'Discrimination in Online Ad Delivery' (original researcher, 2013-01-28) · evidence grade: primary · cited by Check AI ranking, pricing, moderation, and ad targeting for disparities when features can stand in for protected traits