Where risk control requires software items to be kept apart, that segregation is identified, together with an explanation of how it is made effective, for example by running items on separate processors that share no resources, or by other means that the architecture design shows to be effective. Applies to class C.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.