From fb10a9359bfb0d1576f00143452b7fe198400e16 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:27:35 +0100 Subject: [PATCH] Answer A-94: the assigner hears build.ended and maps a want to its release by source Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index e53dfecc..606575ef 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -364,3 +364,8 @@ names the principle that settles it, and is cited as "design 47 G A-n". or bucket of its own; the trunk's `modules`, `manifests` and graph stay the trunk's alone. The trunk stays the mesh-wide branch `main` (ADR 0666's default watched branch), named once in the indexer; a registration's own first branch decides only which of its branches it delivers from. +- **A-94** (§379, §525, §526; principle 1, a part asks for another's data or hears its events) The assigner hears the + builder's `build.ended` event (§379 names it) and reads no builder state such as `build-log`. A want for a trunk + revision's entry takes `version` and its parts' digests from the `version-released` whose `source` is that revision; + a build `build.ended` marks kept (its keeping node) is a kept build, its parts and `kept-on` from that event; a build + of another watched branch is the one whose `build.ended` names that branch, its parts from that event.