Answer A-398: a seat-form read resolves to the assigned claimant when no holder is on record

This commit is contained in:
2026-11-14 18:17:34 +01:00
parent 98e8bc395b
commit f6f82721d5
@@ -903,3 +903,9 @@ the principle that settles it, cited as "design 47 G A-n".
`bus.queues` names. The grants part composes and makes each of them, with the hear of exactly that process's events; a
process that binds a consumer composed for another process is refused at its start, said in its log. This amends
design 19's *one durable consumer per module*, written when a module was one process.
- **A-398** (live, shanks 2026-11-14 18:13: the G builder was refused `KV_mesh-build-go_steps` and the image and node steps,
since its reads `seat:node-build-{go,image,node}.steps` resolved to no holder: no assignments holds the build seats; the
operator decided, 2026-11-14 about 18:16: "yes, do it", after their word of 16:45 that who holds a seat follows from the
module graph and the assignments; principles 1 and 7) A seat-form read, view or view tool resolves to the holder on
record, else to the first module assigned to a node (nodes and modules in name order) whose manifest claims the seat.
Holds keep heldWherePlaced's rule. The whole question of holders stays with the post-G remarks.