At the outset the design team pins down the system's objectives and plans a fairness-aware design with precautions across algorithm, processes and mechanisms so bias cannot produce discriminatory or skewed outcomes. Technical and non-technical members together identify the likely harms and benefits, who is affected including vulnerable groups, and whether the impact is justified by the system's purpose. Fairness assessment metrics are selected now, suited to the algorithm type, the kind of decision it drives (punitive or selective, for instance) and the harm and benefit of correct and incorrect predictions, and sensitive personal attributes of systematically or historically disadvantaged persons or groups are identified with the threshold that separates fair from unfair, to be measured in later steps.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.