From d98e61a6e224ff8d6aa9f58da292a5f776b18f82 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 00:02:43 +0100 Subject: [PATCH] Design 47 H: H-A-381, a repeat of a taken ask answers the act's state; ask-taken-bound --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 3d8e166b..d47b6e9f 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -2387,3 +2387,13 @@ Where two preparers disagreed, the chosen one is named. first. No new store per module (one store per thing, P3). (3) The tools are named as the generic tools are: `_state_prune_now` and `_state_keep` (stateobjects.Tools' form); §812's bare names are the tool kind. P3, P9, P-NATS-native. +- **H-A-381 (a repeat of a taken ask, and the taken key's bound, 00:12)** §775, RG1 and C2. (1) A holder that is asked + again with an id it took follows H-A-364 (b): while the first act still runs the repeat joins it and gets the same + answer; after it ended the repeat answers the act's state as it stands, read afresh (the registry's publish answers + the transfer's parts held; a git verb answers the pull request as it is: merged, with its merge commit), which is + what the act answers when done; the act is never performed twice and no answer is kept in `taken`. A repeat for + which the state says the act never happened (the transfer is gone) is a refusal naming it. (2) The holder never + receives the caller's bound, so the taken key's TTL is a setting of each holder, `ask-taken-bound`, default 10 + minutes (the largest caller's bound, the runner's ask-unanswered-bound), declared in the registry's and the forge + module's manifests; the node-engine keeps compose-ask-bound as H-A-364 (a) decided. §775's "the ask's bound" reads + so. P3, ADR 0668 §2, principle 11.