The guidelines hold their base and the appendix of their tools
The guidelines are divided as the specification is: their base states what is held, what is checked, when, and what a failure costs, and names no technology; the appendix of the tools describes how one toolset carries that base out — its commands, its hooks, where it keeps the files, how it reads code and who runs its reviewer. Each rule of that appendix implements at least one node of the base. The appendix of the tools is not the technical appendix, which describes how the system is built and never the tools of the specification.
The guidelines require of every base specification that it name no technology (§s-5x737t9nee4zgaa) and are held to it themselves: a rule naming its tool goes stale when the tool changes, and another toolset, written in another language, could not implement it. The tools hold the specification and the code to each other rather than make up the system, which is why they are described apart from the technical appendix. Bound to the node of the base it implements, a rule of the appendix is found when that node changes.
The links it makes
The links made to it
The decisions taken on it
- Problem
The guidelines named the commands, the hooks, the files and the parser of the tools that check them, which their own rule forbids a base specification to do.
- Ruling
The owner: the guidelines apply the split between base and appendix to themselves, so that another toolset can implement the same base.