Answer A-96: the builder says build.ended on its own stream

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:28:59 +01:00
parent 4ffcadf4e9
commit 2eb897699f
1 changed files with 6 additions and 0 deletions
@@ -375,3 +375,9 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  words, the node-engine following no view. Still owed in G: a restart composes the bus module and the indexer from the
  kept entries and wants while both are down, without waiting for every input (§683's purpose), and the
  `entry-not-found` finding (§614).
 - **A-96** (§379, G-4's event table, §529, A-67; principles 1 and 7) The builder says `build.ended` itself, as a module
  event on its own stream: a foundation part's old `streams` entry `mesh-delivery-builder-builds`, 7 days, kept last per
  subject `build.ended.<module>.<fingerprint>` (each escaped), its body the build log entry's `module`, `fingerprint`,
  `made` (artifact → digest), `kept-on` and `branch`; the assigner `consumes` `mesh-delivery-builder.build.ended`. A
  want's source revision is the one its pass's kept assignment graph revision was computed from (A-67), matched to
  `version-released.source`; `parts` stay keyed `<module>:<artifact>`, the contract's comment corrected to say so.