New revisions are created only from approved changes, closing the attack in which unreviewed commits on a topic branch become reachable through a merge commit and can be checked out after cloning. Reviewers must be shown the complete content difference between what is now proposed and what they last reviewed (being told only that a file changed is not enough). The protected branch must use a squash strategy: the SCS combines the reviewed diff into one new commit whose single parent is the revision the branch previously pointed to; replaying the topic branch's commits is not acceptable.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.