The developer should make the precision evidence fit both the conditions that may vary in the testing procedure and the interpretations proposed for the scores. The report should name each potential source of error, such as occasion, form, task, or rater, and show how it was handled, whether in one coefficient, a standard error, or a separate analysis.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.