The organization must set a branch protection rule so the branch can point only to revisions with passing test results; tests should run in a trustworthy environment (see the Build track); the change review tool must collect each test result, or an aggregate, and make it available for verification; tests should run on a revision made by merging the proposed changes into the target branch, preferring that merge commit to the tip of the topic branch.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.