// SPDX-License-Identifier: CC-BY-SA-4.0
= Authority and Precedence

== Authority classes

[cols="1,3",options="header"]
|===
|Class |Effect
|constitutional |Highest estate-level constraints on what may govern
|normative |Domain rules within constitutional bounds
|profile |Declared selection or particularisation of upstream rules
|local-policy |Repository-specific binding within higher authority
|guidance |Non-binding explanation or recommended practice
|template |Starting material requiring deliberate adoption
|implementation |Mechanism that may enforce rules but cannot create them
|generated |Derived view whose authority comes only from its source
|historical |Retained context; not current authority
|===

== Precedence test

Apply the highest applicable authority, then the more specific compatible rule. Specificity does not permit a lower class to contradict a higher one. Later text supersedes earlier text only through an authorised change that identifies what it supersedes. Evidence cannot override policy; policy cannot manufacture evidence.

Where requirements conflict, contain harm, preserve evidence, and record a `contradiction` tension. Do not silently choose whichever rule is easiest to automate.

== Normative force

`MUST` expresses an authorised obligation within scope, not an assertion of absolute safety. ALARP decisions address proportional residual risk and MUST record assumptions, alternatives, responsible authority, and review date. ANCHOR is an intervention mechanism, not a standing power to override arbitrary rules; its precedence is limited by link:EXCEPTIONS-AND-ANCHORS.adoc[Exceptions and ANCHORs].
