Expand description
Which declarations an instance’s own specifications do not yet authorize.
A project overruling a specification it owns is exercising ownership, so
nothing here fails. This reads the declarations, reads the sentinel each
one needs, and reports the ones whose sentinel the local specifications
lack. sdd verify prints each as a note, and sdd policy reconcile
offers the correction.
The correction is conservative. It seeds the owning specification where the instance lacks it, and otherwise appends the sentinel’s rule block, taken from the embedded seed, to the end of the local file’s Requirements section. It never rewrites a sentence the project may have edited: a rule block is self-contained, and the unique-id gate catches a collision. A file not in that shape gets a checklist and no write.
Structs§
- Plan
- One reconciliation and what it would do.
- Reconciliation
- One declaration its specification does not authorize.
Enums§
- Action
- What one reconciliation would do.
Functions§
- append_
to_ requirements - The file with the block appended to the end of its Requirements section,
or
Nonewhere the file has no such section to append to. - apply_
all - Carry out every plan as one transaction, and report the files written.
- local_
rule_ ids - Every rule ID the instance’s own specifications define.
- needed
- Every active declaration whose sentinel the local specifications lack.
- plan
- Every reconciliation the target needs, with what each would do.
- rule_
block - The sentinel’s rule block, from the heading to the line before the next heading, as the embedded seed states it.