From acdef3a98d9dcd7c8f10b235af8468032b52dedf Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:13:02 +0100 Subject: [PATCH] Answer A-81: the builder's publish again, as built Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index c68f227c..3e24b271 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -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.`. +- **A-81** (§588, §369; principle 7) As built in mesh-delivery f12883b2: the publish-again queue key is + `..`; 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.