Answer A-151: the build modules read the artifact store through its provision

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:27 +01:00
parent 9e737e7c4c
commit df569ad63a
1 changed files with 4 additions and 0 deletions
@@ -564,3 +564,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-150** (§563, A-107, A-115; principles 1 and 7) restic's `night` process, which dumps, gets a `bus` of its own
  (its own broker account, as the recovery module's process has) and says item-started and item-ended and reads the
  recovery module's events itself; no local request to the tools runtime, and the backup does not move into it.
+- **A-151** (§465, ADR 0614 §2; principle 7) The three build modules `require` the provision `artifact-store` to read a
+  group member's build, with a `binds` file as go-package-registry's (`at`, `serves.port`), and read the blob by the
+  store's own path `<at>:<port>/v2/<module>/<artifact>/blobs/<digest>`; they never write into it, so ADR 0614 §2
+  holds, and their manifest tests assert the read.