The draft sets requirements and recommendations for help content in mobile apps, from first planning through to testing, and it leaves the device hardware itself out of scope. Clause 1 is short and it decides every later argument about scope. It puts the draft in the middle of the product process rather than at the end of it: the help is designed, developed and evaluated, not bolted on after release. It names two routes into mobile help. One is content written for the mobile setting. The other is content that already exists for print, desktop or the web and is transformed by responsive design. The draft keeps the interface hardware out of its own remit. That exclusion is precise: a team still has to make the help readable on the screen it has, but the draft does not specify the screen, the speaker or the sensor.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.