Answer A-73 and A-74: publish again by digest, the router's asks through its seat

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:02:28 +01:00
parent 01b6441a48
commit 0fe2118105
1 changed files with 8 additions and 0 deletions
@@ -275,3 +275,11 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-70** (§572, A-45; the rule that a process answers no call) The builder's tools bundle serves `reserved` and
  `builder_versions`, following the catalog half's view itself as other bundles follow views; the builder's process
  serves no call.
+- **A-73** (§588, §369; principle 7) To publish again, the builder takes each artifact's kind and package name from the
+  catalog entry of the reserved commit, and sends the registry seat's `publish` with the digest and no parts: the
+  holder takes the bytes from the artifact store, addressed by digest (A-50). "Not stored" is the holder's refusal;
+  the entry then ends failed, said with its reason.
+- **A-74** (§700; principle 1, no module names another) The indexer reads the router's `asks` through the seat
+  `operator-channel`: its manifest `uses` that seat, and the bucket is formed from the seat's holder on the seat list
+  and the contract's `StateAsks`, never a module's name in code; the teller's and the node-engine's `messenger_asks`
+  constant goes the same way in their own change.