The organization must restrict sensitive operations on the repository with access controls built on the SCS's identity management (for example only a maintainers role may update main), must configure the SCS to keep a reliable change history for consumable revisions (no extra control is needed if the SCS does so by design; otherwise continuous enforcement must be evidenced), and, where the SCS supports tags, must configure it so tags cannot be moved or deleted.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.