Expand description
The sentinel rules: one per feature a project can declare against its own adopted specifications.
A feature is available the moment the binary carries it. Its normative text arrives as a new adopted specification, seeded on the next upgrade, and each such specification carries one rule that authorizes the declaration. That rule ID is the sentinel. Whether an instance’s specifications authorize what its configuration declares is read by presence of the sentinel and never by matching prose, because a rule ID survives rewording and a sentence does not.
A sentinel never joins a delivered gate’s cites list. That gate check is
always-run, so a cited ID an instance’s specifications lack would fail
every commit in the window between upgrading the binary and running
sdd upgrade. The canon suite holds that boundary.
Structs§
- Sentinel
- One sentinel: the rule, and the adopted specification that owns it.
Constants§
- SENTINELS
- Every sentinel this binary knows.
Functions§
- sentinel
- The sentinel a rule is, if it is one.