All modules

    Module 2.2.1 · Phase 2 Decision · Step 2.2 Populations & IntersectionsCore

    Affected Populations & Intersection Definition

    Which groups and intersections must be tested?

    Defines who the system affects and which groups and intersections must be tested.

    Open in the platform
    Overlapping embroidery hoops. Point at it.

    What it does

    You set the population scope, register protected attributes, rank intersections as must, should or optional with a sample-size check, and list likely proxies. Measured subgroup disparities on your dataset support the scope, which ends in a recorded approval.

    Why it matters

    This step formally defines which populations and intersectional groups are entitled to fairness guarantees and which are excluded, with documented rationale. It makes intersectionality an explicit, auditable decision rather than an implicit byproduct of data availability or metric choice.

    Step 2.2, Affected Populations & Intersection Definition, in the Decision phase.

    Where it sits

    1. 2.1Fairness Definition
    2. 2.2Populations & Intersections
    3. 2.3Bias Identification & Prioritization
    4. 2.4Metrics & Thresholds
    • 2.2.1Affected Populations & Intersection Definition

    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 2.2.1 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.