Operating conditions can drift from the domain on which the system was specified and validated, especially in an open world. Assessing robustness in operation shows whether the domain of operation is deviating too far, so that corrective action (an operator alert, a switch to fail-safe mode) follows when the required level is not reached. Since networks behave similarly on similar inputs, a local property such as stability can reveal whether new inputs still belong to the trained domain. When assessing robustness over a new domain, the result a criterion gives on fresh inputs should be compared regularly with the outcome of the same criterion at the previous life cycle stage.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.