Design 47 H: H-A-153, the composition run value carries its unlisted set

This commit is contained in:
2026-11-20 16:45:35 +01:00
parent 291f12fc5f
commit 94f45529cd
@@ -755,3 +755,9 @@ Where two preparers disagreed, the chosen one is named.
while a machine still holds it assigned stays in the composition and fails it as "nothing provides", the change's own
fault (ADR 0578 §2), never a stale assignment. Where the newest revisions are not followed yet, nothing is unlisted
and nothing is left out. P3, P7.
- **H-A-153 (the run value carries its unlisted set, 16:52)** Met in the build of H-A-152: the judgement and the
resume after a restart read only the stored run (state `composition-runs`), and no field of the run value (G-24 §719)
holds the set; the kept request is gone before the judgement. The run value gains the field `unlisted`, the module
names of the assignments left out, written when the run starts and read by every step's judgement and by the
resume, in the seat mesh-wants' definition and its generated contracts; a change of the seat's definition is a group
with the assigner, one check. State the judgement needs lives on the bus, never only in the step's memory. P1, P7.