Module 4.2.3 · Phase 4 Enforcement · Step 4.2 Release GateSupplemental
CI/CD Integration
How are fairness checks run before every deployment?
Brings fairness checks into your deployment pipeline, so retrained models and changed data are checked before they ship.
What it does
You set fairness gates with block or warn thresholds per metric, a pytest or unittest test suite and data validation checks. You get four starting files for your repository: gate configuration, test suite, data validation and pre-commit hook.
Why it matters
This step decides whether the system may be released. It checks the release against the regulatory obligations that apply and the written fairness policy, records a binding go or no-go decision, and makes the same check run on every later release.
Where it sits
- Validation
- Release Gate
- Operating Model
- Scrum Fairness Oversight
- Compliance Pathway Navigator
- Fairness DoD Gate
- CI/CD Integration
How to use it
In the Fairness Navigator Beta
Work through the steps in order. Several modules open from the Navigator's steps and hand their results back.
On its own Live
Open 4.2.3 from the platform's Modules page and run it when your project needs it. Work is saved with the assessment.
After a Pulse reading Live
Start with a fast first read, then go deeper with the modules where it points.