Design 47 H: H-A-381, a repeat of a taken ask answers the act's state; ask-taken-bound

This commit is contained in:
2026-11-22 00:02:43 +01:00
parent bc1c1561f3
commit d98e61a6e2
@@ -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:
`<module>_state_prune_now` and `<module>_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.