From fbb60b952ca0cace59796988d9f2df02688e56d4 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:00:43 +0100 Subject: [PATCH] Answer A-211: the assigner's put waits in a state of their own Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 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 ab0ccc50..6bebed04 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 @@ -130,3 +130,6 @@ the principle that settles it, cited as "design 47 G A-n". asking again after a failure and never stopping its start for it; a read of another module's bucket goes (each by its own row). A tool's callers list names no module: it takes the holders of the seats `node-tool-runner` and `mesh-healers` from the seat list when a call is checked, beside `operator`. +- **A-211** (A-204; principles 2 and 7) The assigner's said put waits live in a state of their own, `put-waits` + (history 1, key `.`, value the wait's id and the put), so no form is shared with ยง706's waits and the + record outlives a supersede.