From f55a6e7927906ab32aef3918084a7f250fe58cea Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:39:47 +0100 Subject: [PATCH] Answer A-399: a seat pulled by kind's holder says the seat's own events --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 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 7f7934a3..283be323 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 @@ -909,3 +909,10 @@ the principle that settles it, cited as "design 47 G A-n". 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. +- **A-399** (live, shanks 2026-11-14 18:32: the Go build seat was refused `toolchain-reported.shanks`, and `step-ended` too: a + seat pulled by kind is composed by the seat-traffic rules, which grant an event only under a kind or a caller's name, and + the held-seat rule skips such a seat, so its own events were granted to nobody and the builder heard no toolchain; + principle 7, and who-may-is-not-the-operators-question) The holder of a seat pulled by kind (not kinded) says each of the + seat's events no caller names: on its own machine in its account where the definition's subject names `` + (machineEvent now reads `` 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.