arXiv (All)
open access
When Post-Processing Fairness Constraints Help and When They Harm: Evidence from Eight Cross-Domain Evaluations
Fairness audits in production ML typically occur once, at deployment, on a single domain. Both fail in practice: fairness can shift after retraining or a changing user base, and interventions validated on one dataset are rarely tested across the heterogeneous domains an organization deploys. We pres
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Be Fair! Can Machine Learning Engineering Agents Adhere to Fairness Constraints?#259590
- Bridging fairness in machine learning: A legal critique of technical strategies#1178550
- When Fairness Metrics Disagree: Evaluating the Reliability of Demographic Fairness Assessment in Machine Learning#19024
- Tracing Fairness Disparities Across the Machine Learning Pipeline: A Stage-Resolved Bias Provenance and Propagation Framework for Educational Prediction#413050
- FeDa4Fair: Client-Level Federated Datasets for Fairness Evaluation#158741
Record · ID 1063166
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive