Changes to protected branches must be agreed by two or more trusted persons before submission, either an uploader and a reviewer who are different trusted persons or two different trusted reviewers; reviews should cover at least the security-relevant properties of the code. The approval applies to the final revision submitted, so later changes during review must be reviewed too; approvals are for one context (such as a repository and branch), so moving reviewed content elsewhere needs review again, routine automatic merges such as creating a release branch excepted; the SCS must show reviewers plainly what accepting the change would produce. The organization may grant a trusted robot (for example an import bot or a dependency update bot) a standing exception.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.