ADR 0259 (proposed): let any module ask a person and any channel answer, so Telegram is not built into the controller

2026-10-09 15:36:36 +02:00
parent 80b02dc9a0
commit 9f66452fff
3 changed files with 333 additions and 1 deletions
@@ -477,7 +477,11 @@ asking, never the act. **Decided by** ADR 0152, 0175, 0234, 0272.
  ([ADR 0253](../02-DECISIONS/0253-a-condition-says-itself-to-the-operator-in-plain-words-beside-its-summary.md)).
 - **ask** — a request for the operator's input, of a declared kind (yes-no, one-of, text, number,
  date, acknowledge). An **authorising ask** is one whose answer performs an action; the controller
-  holds it and checks its proofs (ADR 0234).
+  holds it and checks its proofs (ADR 0234). *Proposed in ADR 0259:* the router holds every ask, and
+  the asker performs the chosen option on a **warrant**.
+- **warrant** — the router's record that a person chose one option of one ask: the ask, the option,
+  who chose (the operator, as a channel kind's identity), through which channel, the proofs and when,
+  published for that asker alone. The only thing an asker acts on (ADR 0259, proposed).
 - **operator message / input** — what arrives on `intake`, once the router has checked the sender
  against the controller's list of the operator's identities: a **trusted** one is an operator message,
  addressed to an agent by `@name` or thread or else to the **responder** (`@mesh`, the router's own