Answer A-57: the builder's package-published, whole, with its branch and source

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:45:25 +01:00
parent 927ff51842
commit ac217628a1
1 changed files with 5 additions and 0 deletions
@@ -218,3 +218,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-56** (ADR 0573 §2, §4; principle 5, everything ships the same way) The locks check treats every `@novox/mesh-*`
  package as it treats the SDK's, since the builder builds a module against the latest published version of each mesh
  package as it does for Go; the order between the contracts' publish and gitea's build is the delivery plan's.
+- **A-57** (§466, §52, §334, §349, §371; principle 7) BL1 is the whole `package-published` emission, built after BL5's
+  watched-branch half: the builder says it per artifact when it hears the registry seat's `published`, carrying
+  `resolved` and `toolchain` from the step's result (`dependencies`, §673), `branch` the watched branch of the catalog
+  revision whose entry the build came from, and `source` that revision, both kept on the build's reservation from the
+  candidate it built.