4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	5ebb3520ec	asks: the live acceptance says when a new link can approve, and asks through mesh-cli ... Step 3 stopped silently 16 minutes later when the Telegram account was linked less than an hour before; it now says that approvals start at the local time the router gives. The script reaches the controller through mesh-cli, the controller's terminal on the control node (hq ADR 0272).	2026-10-09 15:37:57 +02:00
jschoubben	70bc7ad3db	asks: the live acceptance reads root-not-free, and gives the bot token at the controller's terminal	2026-10-09 14:26:19 +02:00
jschoubben	01a541cadf	asks: prove the reviewed flow — the controller's root-free word asked before an approval, the desk on its own account, a tap only on the words shown, the question saying who asks and what each answer does, and a rehearsal at the terminal for the live acceptance	2026-10-09 12:44:21 +02:00
jschoubben	3a486014fc	Prove the operator's answers end to end before anybody uses them (hq ADR 0259) ... The bus the controller composes and raises, at its commit, for one machine; the mesh's runtime serving the router and the Telegram channel on their own credentials; a fake Bot API as the phone. It links the operator's account with the code shown on the desk, refuses an approval in the hour after a link, performs an approval exactly once with who and how in the warrant and the router's record, refuses a replayed tap and a redelivered warrant, tells the operator when another account answers, drops a tap from a group, does nothing on Decline and on expiry, offers no approval while an agent can become root where the channel runs, and has the bus refuse every forged warrant, ask and tap. live-acceptance.sh is the same after rollout, with a drill the operator approves on the phone.	2026-10-09 11:08:42 +02:00