Competent test users should survey current information on the tests that might suit, using specimen sets, independent reviews and expert opinion, before settling on one. They should check that the technical and user documentation says enough about content coverage, norm groups, reliability, validity for the intended use, freedom from bias, acceptability to those involved, and practical cost and time. They should turn down tests whose technical support is weak or unclear, and should use a test only for purposes that its validity evidence actually covers. They should not judge a test on face value, on user testimonials or on the word of someone with a commercial interest, and should be ready to explain to test takers, parents or managers why a particular test was chosen.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.