Answer A-250: delivered-again is an ask the assigner's process judges

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 7e9bb2dab4
commit 637df7d374
1 changed files with 5 additions and 0 deletions
@@ -270,3 +270,8 @@ the principle that settles it, cited as "design 47 G A-n".
  runner receives the chunks with `buscalls.SeatChunks` and hands the bundle the whole answer, so no bundle receives
  chunks itself. mesh-build-go's `inputOf` calls the mesh-catalog seat's `input` that way and decodes that verb's
  own answer form.
+- **A-250** (§376; principles 1, 2 and 4) `assigner_delivered_again` writes the hand-act log, then an ask in the
+  assigner's own state `delivered-again` (key the module, value {version, by, why}) and answers "asked". The
+  assigner's process hears that write on its own state at once, says `version-delivered` again when every present
+  placing machine runs the version healthy and deletes the ask, else keeps it with its reason, read by
+  `assigner_waits`.