Answer A-400: seat-holders names the assigned claimant of a seat no assignments holds

This commit is contained in:
2026-11-14 20:21:29 +01:00
parent 232454cf76
commit d5e7d42d17
@@ -916,3 +916,12 @@ the principle that settles it, cited as "design 47 G A-n".
seat's events no caller names: on its own machine in its account where the definition's subject names `<node>`
(machineEvent now reads `<node>` from any node seat's event subject, not the node-engine's alone), and with any machine in
its membership, since the runtime carrying it checks the membership; the account is therefore granted any machine's too.
- **A-400** (live, the control-node 2026-11-14 19:12: the indexer waited for ever on the view `seat:mesh-module-assigner.assignments`
for a holder of the seat, since the assigner's state seat-holders is written from the assignments' holds alone and no
assignments holds mesh-module-assigner; its versions fill stayed undone and no build began; the operator, 2026-11-14 about
16:45 and 18:16, as for A-398; principles 1 and 7) The assigner writes seat-holders from the assignments' holds and, for
each seat no holding names (a seat held once: on no node; a seat of every node: on that node), the first module assigned
to a node (nodes and modules in name order) whose manifest of the trunk claims it: the same rule as A-398, in the
writer every reader of the holders reads. It says each key so derived once, and when it stops being derived. The
assignment graph's requirement resolution and the order waits keep reading holders from the holds alone; the post-G
remarks take that up with the rest of the holders question.