Operational constraint asks whether the product respects the conditions it must operate within. A measure relates constraint violations to the operating period or the operations observed. A constraint is a limit the product must not cross: a speed, a dose, a temperature, a concurrent user count, a data retention period. The measure is a count of violations or a proportion of operations within limits. The constraints have to come from the hazard analysis or the domain, not from the product's current behaviour, because a product that has always exceeded a limit has not defined it. The measure should record the operating envelope and what happens at the boundary.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.