Design 47 H: H-A-239, the warrant ask's expiry bounds; the router's standing is read, not waited for

This commit is contained in:
2026-11-21 11:11:22 +01:00
parent 9b23a021e5
commit 99c3081d9b
@@ -1344,3 +1344,11 @@ Where two preparers disagreed, the chosen one is named.
armed before the ask is put and deleted at the first word; its expiry asks once more with a journal line and
re-arms as ask2.<seat>.<ask>; that expiry ends the step could-not-run "its ask <id> was not answered": a restart
of the runner loses no bound. P2 (state on the bus), P4, P7 (the drop bound's form reused).
- **H-A-239 (the warrant ask's expiry bounds; the router's standing is read, not waited for, 11:11)** Amends H-A-237.
(1) expires_minutes is 5 to 1430 (the channel's own bounds), a value outside refused with its bounds named, never
clamped; the keeper's fallback where the router holds no record is the ask's own expiry as asked (the default
sixty minutes), not the longest. (2) The tool makes one read of the router's record right after the publish and
answers what it finds: offered (where), held (why), refused (why), or "raised, not yet taken in by the router: read
the request for its standing"; no timer waits on the router. The request read (the tool's argument)
shows the router's standing of the ask beside the keeper's. P-NATS-native (no part waits on a timer for another),
P4 (what is said is what was read).