Design 47 H: H-A-149, the finding of an unlisted assignment

This commit is contained in:
2026-11-20 16:27:29 +01:00
parent 310f8955ba
commit fed78cceeb
@@ -730,3 +730,9 @@ Where two preparers disagreed, the chosen one is named.
condition on the assignment, never as the machine's failure: a stale assignment is a fault of the assignments, not
of the change under judgement (ADR 0578 §2). A module the catalog lists with no registration (the wireguard module
today) is registered through the catalog's verb; until then it is unlisted by H-A-144 and left out alike. P3, P7.
- **H-A-149 (the finding of an unlisted assignment, 16:30)** Met in the build of H-A-148: the assigner's findings (its
state `findings`, the condition keeper raises and clears them) need the finding's form. Kind `assignment-unlisted`,
scope `delivery`, id `<node>.<module>`, severity warning, raised by the composition step that leaves the assignment
out. It clears where the assignments are judged, not only where a machine is composed: the assigner clears it in its
pass over the assignments (the one that writes wants) when the assignment is gone or the module is listed again, so
the clear does not wait for the next step on that machine. P3.