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
2026-11-11 23:27:35 +01:00
parent d0beb962d8
commit fb10a9359b
1 changed files with 5 additions and 0 deletions
@@ -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.