Answer A-83: a branch build's edges and its newest build

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:15:40 +01:00
parent 2f8e07d923
commit 1963baefb3
1 changed files with 4 additions and 0 deletions
@@ -323,3 +323,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `builder_stuck` all derive from it, and `builder_stuck` reads each build seat's steps through the seat (`<seat>.steps`)
  rather than a named module's state. The floor's sources are the holders of the seats `git` (tags) and `mesh-catalog`
  (requirements) on the seat list.
+- **A-83** (§374, A-78, A-80; principles 1 and 7) `BuildEdges.fp` is the fingerprint of the branch's catalog entry at
+  the revision `source` names, which the indexer holds itself; no field is added to `package-published`. For a build
+  of another watched branch, kind 1 compares with that branch's newest build, kept as heard in `heard` as
+  `branch-build.<module>.<branch>` (the digest `package-published` carries), not with a released digest.