From 637df7d374545e716922279bd1312d8d1c88da7a Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 09:22:06 +0100 Subject: [PATCH] Answer A-250: delivered-again is an ask the assigner's process judges Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 680da938..52b47964 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -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`.