Answer A-81: the builder's publish again, as built

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:13:02 +01:00
parent 9d406b6f02
commit acdef3a98d
1 changed files with 5 additions and 0 deletions
@@ -311,3 +311,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `delivered`, `pending`, `acted`) lives in one state of its own, `heard`, not in `own-build`, which keeps its one key;
  every key part is escaped as a name (§73), so a dotted module name parses; a kind-3 edge compares its artifact's
  language with `toolchain.<language>`.
+- **A-81** (§588, §369; principle 7) As built in mesh-delivery f12883b2: the publish-again queue key is
+  `<holder>.<module>.<version>`; the holders and their nodes are what the builder hears on `running` (read whole at its
+  start, §556, so a restart rebuilds them); `running` means not stopped, with a fingerprint; a not-stored artifact is
+  remembered on the reservation (`Unstored`); the tool's request rides a reasks mode `republish`; a message the state
+  cannot take is not acknowledged, as the other parts do.