To-be 46: the session gets its key within seconds, not at once (review of #334)
The tool waits for the router's word before it answers, as ADR 0332 §5 says.
This commit is contained in:
@@ -218,7 +218,7 @@ is the asker: the ask goes out under that module's own name, so the bus proves w
|
||||
gains no verb. The session gives a headline, the context in plain words, two to four options with exactly
|
||||
one recommended and why, what it does if nobody answers, its own name, and an expiry of five minutes to a
|
||||
day less ten minutes. Every option is an approval bound to the question, so only a channel that proves who
|
||||
answered carries it, never the desk. The session gets a key at once and reads the answer by it later:
|
||||
answered carries it, never the desk. The session gets a key within seconds and reads the answer by it later:
|
||||
waiting, the option chosen with who chose it and where, ended without a choice, or not proven when the
|
||||
router's record does not hold to the question asked. At most two such questions are open at once, so one
|
||||
open ask is always left for a proposed instruction section. The answer informs the session and authorises
|
||||
|
||||
Reference in New Issue
Block a user