Once the work instruction is written it is compared against the design, with evidence showing how it conforms; the design may be updated for changes made while writing the instruction (for example unexpected tool behaviour). This is normally done by white box testing so the two can be compared.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.