From f6f82721d5d4deec586619c8feb65555f27ccf35 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:17:34 +0100 Subject: [PATCH] Answer A-398: a seat-form read resolves to the assigned claimant when no holder is on record --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 1aff7b0b..7f7934a3 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -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.