Rendered from docs/obligations/0188-the-negative-compliance-edge-and-the-governance-precedence-clause-contradict.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

The negative compliance edge and the governance precedence clause contradict

Context

Spec 2 spells does_not_comply_with from the deviating document to the standard, inside the governance family. The derived precedence of that family makes the source of the edge govern. So the document that violates a standard governs the reading of the standard it violates.

The standards-spec entry met this when it spelled its positive edge. It spells that edge from the standard, which is the only spelling the precedence clause permits. The two edges of one tradition then point opposite ways. The second finding at line 154 of the doctrine holds the argument.

Obligation

Either the family assignment of the negative edge or the precedence clause is wrong, and no reading makes both right. The owner owes one of two changes to spec 2. The negative edge leaves the governance family, or the precedence clause stops deriving direction from the source of an edge.

Nothing measures the contradiction today, because no corpus here holds such an edge. HW-OBL-0187 records why no entry can declare the relation at all.

Discharge

This record discharges when spec 2 states one direction and one family for the negative edge, with the reason. The ruling is cheap now and expensive after the first adopter writes a deviation. The direction is then in a corpus that a migration has to rewrite.