Research 028: a conversation with the operator over channels that are seats; Telegram as first holder #139

2026-10-06T14:17:16Z

mesh-admin commented

2026-10-06 14:17:16 +00:00

Research only, following playbook 01. Research 028 is widened rather than a new effort opened: its Q1, Q4, Q7 and Q8 own the question, and ADR 0227 left answering back open here. The overview says why.

Documents, in reading order:

04: Telegram as the first holder. Making the bot, Bot API facts, what Telegram sees, failure modes, cost, and defects D1-D10 in the built Telegram code.
05: ntfy, Matrix, Pushover, Gotify, mail, Signal, SMS and an outside dead-man service, each judged as the away channel and as the watcher's path.
06: a conversation with the operator, the core model. It covers messages, asks (yes-no, one-of, text, number, date, acknowledge; with timeouts, defaults, cancellation, batching and history) and messages the operator writes first; the kinded benches channel and intake; the capability vocabulary with a contract test per capability; and agents as participants.
07: the work context and the desk. Routing by context with escalation; presence kept inside the mesh; desktop actions and the launcher's prompt as a full participant.
08: asks that authorise, a layer on top. The actions that need a person; trust capabilities; three proofs (a verified Telegram sender, a TOTP code, a security-key touch bound to the ask); acknowledge, approve and destroy tiers; the controller's authorise request / authorise answer; why a click on the X11 desk needs a factor; what a compromise exposes.
09: the recommendation, the operator's steps, the tables, and a proposed record ready for graduation.

Checks: records, index and cycle all pass. Not to be merged without a human review.

Research only, following playbook 01. Research 028 is widened rather than a new effort opened: its Q1, Q4, Q7 and Q8 own the question, and ADR 0227 left answering back open here. The overview says why. Documents, in reading order: - 04: Telegram as the first holder. Making the bot, Bot API facts, what Telegram sees, failure modes, cost, and defects D1-D10 in the built Telegram code. - 05: ntfy, Matrix, Pushover, Gotify, mail, Signal, SMS and an outside dead-man service, each judged as the away channel and as the watcher's path. - 06: a conversation with the operator, the core model. It covers messages, asks (yes-no, one-of, text, number, date, acknowledge; with timeouts, defaults, cancellation, batching and history) and messages the operator writes first; the kinded benches `channel` and `intake`; the capability vocabulary with a contract test per capability; and agents as participants. - 07: the work context and the desk. Routing by context with escalation; presence kept inside the mesh; desktop actions and the launcher's prompt as a full participant. - 08: asks that authorise, a layer on top. The actions that need a person; trust capabilities; three proofs (a verified Telegram sender, a TOTP code, a security-key touch bound to the ask); acknowledge, approve and destroy tiers; the controller's `authorise request` / `authorise answer`; why a click on the X11 desk needs a factor; what a compromise exposes. - 09: the recommendation, the operator's steps, the tables, and a proposed record ready for graduation. Checks: records, index and cycle all pass. Not to be merged without a human review.

mesh-admin added 1 commit 2026-10-06 14:17:17 +00:00

Research 028: channels and intake as seats, decisions from a channel, Telegram as first holder 62db332b3e

The operator asked to approve and reject through Telegram, for a generic shape in which a
channel holds a seat, for input triggers, and for capabilities that decide which actions travel
where. Widen 028 rather than open a new effort, since its Q1, Q7 and Q8 own the question.

jschoubben added 1 commit 2026-10-06 14:24:26 +00:00

Research 028: frame it as a conversation with the operator; add asks, work context and the desk b140ac9af7

The operator widened the direction: asks need not be about permission, the work context picks
the channel, and desktop buttons should serve at the desk. Make the conversation the core model
and keep authorisation as a layer on top, with proofs a desk click alone cannot give.

mesh-admin changed title from ~~Research 028: channels and intake as seats, decisions from a channel, Telegram as first holder~~ to Research 028: a conversation with the operator over channels that are seats; Telegram as first holder

2026-10-06 14:24:39 +00:00

mesh-admin merged commit e77ce351cd into main

2026-10-06 14:33:22 +00:00

mesh-admin deleted branch research/028-telegram-channels-and-triggers

2026-10-06 14:33:22 +00:00

mesh-admin commented

2026-10-06 23:08:08 +00:00

Delivery novox/hq@e77ce351cdb9 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#139 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@e77ce351cdb9` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#139 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin referenced this pull request

2026-10-08 10:04:57 +00:00

ADR 0252: a module puts an account in a group, and the mesh says when a new login is needed #201

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#139