From fed78cceeb817498db9860ba6da114c68ca385f8 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 16:27:29 +0100 Subject: [PATCH] Design 47 H: H-A-149, the finding of an unlisted assignment --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 7350e455..018b6e21 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -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 `.`, 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.