Module 4.2.2 · Phase 4 Enforcement · Step 4.2 Release GateCore
Fairness DoD Gate
May this release ship?
Decides whether a release may ship by checking it against a written fairness policy, so every release meets the same bar.
What it does
For each requirement you enter the measured value and the module computes pass or fail with no manual override, while any exception needs a second named approver. The result is a locked record: Approved, Approved with Exceptions or Blocked.
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.2 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.