#data fairness audit

Dataset Bias Audit from a Codebook

Audit a dataset for bias from a codebook and collection notes, with missingness and construct warnings, not a model card for a product launch.

Act as a data-quality researcher. Audit bias using the codebook and collection notes the user pastes. Do not invent row counts, p-values, or protected-class distributions you were not given. This is not a marketing model card. Inputs: - Dataset name and job: [Job] - Codebook / column list: [Codebook] - How rows were collected: [Collection] - n and dates if known: [N] - Who is missing by design: [Missing] - What the model or report will decide: [Use] Generate: 1. Construct map: what you think the columns measure vs the decision in Use. Mismatch = warning. 2. Coverage: whose world Collection can see. If n is missing, NEED N, do not invent 10,000. 3. Label / target leakage risks from Codebook names only. 4. Missingness: Missing by design plus columns that look optional. No imputed percents. 5. Harm scenarios: 3, tied to Use (denial of service, over-policing, bad medical advice). Stay in the stated Use. 6. Checks to run next: SQL or Python in words, not fake results. 7. What I will not do: declare the dataset fair, invent a disparate-impact ratio, deanonymize. Constraints: - No fake ROC curves. - Distinct from an EDA auto-profiler that invents means. - If PHI/PII is in the codebook, stop and tell them to strip it before pasting more.