Answer A-54 to A-56: distribution's old stream name, the builder's setting, mesh TS packages in the locks check

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:45:11 +01:00
parent 7ee9271a3b
commit 927ff51842
1 changed files with 8 additions and 0 deletions
@@ -210,3 +210,11 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-53** (§681, ADR 0675; principles 3 and 7) A snapshot's record never ages out before its file: the bus module's
  `requests` state keeps its records 91 days (one more than `snapshot-keep-days`), and the keeper removes a snapshot's
  record together with its file at expiry, so no file is left without a record and no record without its file.
+- **A-54** (§584, ADR 0363; principle 8) Distribution's old-section stream takes the old form's name beside
+  `<module>-findings`: `distribution-events`, never the mesh's own `events`.
+- **A-55** (§672, ADR 0348 §5; principle 7) The builder's `toolchain-wait-minutes` reaches it the way the mesh fills a
+  part's settings, as mesh-conditions reads its own (the runtime's settings read at start, the manifest marking it
+  `runtime`), never through the process's environment.
+- **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.