To-be 46: the session gets its key within seconds, not at once (review of #334)
mesh/merge-gate head f7c677a3a712 merged into trunk 87f24d6b6903 — pass: the change touches no module of the mesh's graph
mesh/repo-check head f7c677a3a712 merged into trunk 87f24d6b6903 — pass: its merge-check.sh passed
mesh/delivery delivered

The tool waits for the router's word before it answers, as ADR 0332 §5 says.
This commit is contained in:
jochen
2026-10-12 23:15:12 +02:00
parent a5333f8ecb
commit f7c677a3a7
@@ -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