The changes check as a rule plugin of Mizan (commons 0020-ifccmFR-032), for what a folder of specifications can judge offline: the shape of a harness's declaration (a regulated domain claimed with no production day). The rules that read commits need a range and are the command's (changes.ts).
A plugin runs once for each specification, and a declaration is one for the harness, so the plugin reports it only for the specification it is anchored to (the first of the folder), and holdHarness anchors it. A finding of it is in the gate phase: a declaration that is wrong by itself is refused whatever the baseline holds.