merge-authority
The method's canonical merge-authority contract: for each loop model, who executes a merge, the verdict literals, the complete human-hold set and how the safe and boundary classes relate; and the one block a project brief declares instead of restating it (its loop model and its own boundary triggers). Use when classifying a merge, writing or reading a gate verdict, deciding who merges, or writing a project brief's merge section. A project may add boundary triggers; it may not change the executor, the verdicts or the holds.
Pinned to revision cd25a4dfb3ef, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.