From b75c04f038fab2fe9e0dce584b61b2b888b20335 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 18:56:49 +0100 Subject: [PATCH] Answer A-298: one shared follower of the seat-holders view in the catalog seat's client Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 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 9c33975e..7b8a6a2d 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 @@ -459,3 +459,9 @@ the principle that settles it, cited as "design 47 G A-n". form: base 36 of the pipeline's start time in milliseconds, then six hex digits of the sha256 of the pipeline, the artifact and the step, so the same placement makes the same id at every start (and the bus dedupes on it); a rerun uses its own start time. +- **A-298** (§717, §614, §616, A-295; principle 7, one shared mechanism) The claimant of a seat is read from the + catalog half in one place, the catalog seat's client (`Branches.Claimant(seat)`), and one follower there follows + the claimant's seat-holders view, drops and follows again on each catalog change, and answers the SDK's holder + function; every part calls it once and FollowSeat builds on it. The assigner answers its own holder function from + its own seat-holders picture. The seat-holders first-view tool names its callers in A-131's module form for now + (the teller holds no seat to be named by); naming them by seat waits for every follower to hold one.