Standards governing how requirements, design and code are to be written are set up for the project. Table A-1 objective 5, described in 4.1.e; applies at levels A, B, C, no independence required; activities 4.2.b, 4.2.g, 4.5; outputs: the Software Code, Software Design and Software Requirements Standards. The code standard both keeps source consistent and verifiable and can ban language features that complicate verification or create safety risk; standards may also define mechanisms that improve robustness.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.