To-be 46: an agent session asks the operator through its module and reads the answer by a key (issue 589, ADR 0332) #334

Merged
mesh-admin merged 2 commits from design/589-a-session-asks-the-operator into main 2026-10-12 21:30:23 +00:00
Contributor

Gives ADR 0332 its home: a subsection of to-be 46 §6 (asks), "An agent session asks", and ADR 0332 in the design's decisions.

Why: issue 589, the operator wants decisions asked on Telegram so a session is not blocked at the terminal. ADR 0332 is proposed, approved by the knowledge base's review (version 6), and waits for the operator's Approve.

Tested: merge-check.sh (records, index, cycle, words) passes locally.

Code: novox/mesh-catalog fix/589-a-session-asks-the-operator.

Fixes issue 589 (design part).

Gives ADR 0332 its home: a subsection of to-be 46 §6 (asks), "An agent session asks", and ADR 0332 in the design's decisions. Why: issue 589, the operator wants decisions asked on Telegram so a session is not blocked at the terminal. ADR 0332 is proposed, approved by the knowledge base's review (version 6), and waits for the operator's Approve. Tested: merge-check.sh (records, index, cycle, words) passes locally. Code: novox/mesh-catalog fix/589-a-session-asks-the-operator. Fixes issue 589 (design part).
mesh-admin added 1 commit 2026-10-12 20:45:12 +00:00
To-be 46: an agent session asks the operator through its module and reads the answer by a key (issue 589, ADR 0332)
mesh/merge-gate head a5333f8ecbcc merged into trunk 87f24d6b6903 — pass: the change touches no module of the mesh's graph
mesh/repo-check head a5333f8ecbcc merged into trunk 87f24d6b6903 — pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
a5333f8ecb
Gives ADR 0332 its home in the design of the conversation with the operator, beside how an asker gets its answer.
Author
Contributor

Delivery novox/hq@f7c677a3a712 — delivered since 2026-10-12T21:30:52Z

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

Transitions

  • 2026-10-12 21:15 (new) → proposed (announced): novox/hq#334's head announced
  • 2026-10-12 21:16 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-12 21:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-12 21:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-12 21:30 published → delivered (done): nothing for a walk to move

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

<!-- mesh-delivery:view --> **Delivery** `novox/hq@f7c677a3a712` — **delivered** since 2026-10-12T21:30:52Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-12 21:15 (new) → proposed (announced): novox/hq#334's head announced - 2026-10-12 21:16 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-12 21:16 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-12 21:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-12 21:30 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-admin left a comment
Author
Contributor

Verdict: approve at a5333f8ecb

Independent review of to-be 46's new section "An agent session asks" against ADR 0332 (accepted, version 8), issue 589.

  • The section matches the ADR's clauses. The module is the asker under its own name and the router gains no verb (1). The fields and the expiry bounds are those of clause 2. Every option is an approval bound to the question, so only a channel that proves who answered carries it, never the desk (4). The four read states match clause 5 and the not-proven rule matches clause 6. The cap of two leaves one ask for a proposal (8). An answer authorises nothing (7). "ADR 0332" was added to the frontmatter decisions.
  • The text is public-safe: role words only, no node names, paths or addresses. "agent module" is the glossary's usage.
  • I ran bash merge-check.sh at this head with MESH_CATALOG_DIR set: records, index, cycle (436 documents) and words all pass. (The file has no exec bit in my clone, so ./merge-check.sh was refused with permission denied; through bash it passes.)
  • Statuses at this head: mesh/merge-gate success (it touches no module), mesh/repo-check success, mesh/delivery success.

One nit, not blocking: "The session gets a key at once" says more than clause 5, under which the tool first waits up to a few seconds for the router's word. "gets a key within seconds" would match.

The catalogue pull request (mesh-catalog #258) has requested changes: a secret-shaped question is kept on the bus before the router refuses it. This design text does not depend on that fix.

Verdict: approve at a5333f8ecbccf77ad4bbe1ba6a4144007e3be874 Independent review of to-be 46's new section "An agent session asks" against ADR 0332 (accepted, version 8), issue 589. - The section matches the ADR's clauses. The module is the asker under its own name and the router gains no verb (1). The fields and the expiry bounds are those of clause 2. Every option is an approval bound to the question, so only a channel that proves who answered carries it, never the desk (4). The four read states match clause 5 and the not-proven rule matches clause 6. The cap of two leaves one ask for a proposal (8). An answer authorises nothing (7). "ADR 0332" was added to the frontmatter decisions. - The text is public-safe: role words only, no node names, paths or addresses. "agent module" is the glossary's usage. - I ran bash merge-check.sh at this head with MESH_CATALOG_DIR set: records, index, cycle (436 documents) and words all pass. (The file has no exec bit in my clone, so ./merge-check.sh was refused with permission denied; through bash it passes.) - Statuses at this head: mesh/merge-gate success (it touches no module), mesh/repo-check success, mesh/delivery success. One nit, not blocking: "The session gets a key at once" says more than clause 5, under which the tool first waits up to a few seconds for the router's word. "gets a key within seconds" would match. The catalogue pull request (mesh-catalog #258) has requested changes: a secret-shaped question is kept on the bus before the router refuses it. This design text does not depend on that fix.
jschoubben added 1 commit 2026-10-12 21:15:14 +00:00
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
f7c677a3a7
The tool waits for the router's word before it answers, as ADR 0332 §5 says.
mesh-admin left a comment
Author
Contributor

Verdict: approve at f7c677a3a7

Re-review against my review 106. The one change since then is the nit I raised: "gets a key at once" now reads "gets a key within seconds", which matches ADR 0332 clause 5. The section still matches the ADR clause by clause and is public-safe. bash merge-check.sh with MESH_CATALOG_DIR set passes: records, index, cycle (436 documents) and words. The latest mesh/merge-gate, mesh/repo-check and mesh/delivery on this head are success.

mesh-catalog #258 still has one change requested: the two-minute release of an unrecorded question. The fix for it does not change this design text unless the catalogue chooses to cancel such a question. In that case, one sentence here should say so.

Verdict: approve at f7c677a3a712f3584d76719a13fd868a4e34ca9a Re-review against my review 106. The one change since then is the nit I raised: "gets a key at once" now reads "gets a key within seconds", which matches ADR 0332 clause 5. The section still matches the ADR clause by clause and is public-safe. bash merge-check.sh with MESH_CATALOG_DIR set passes: records, index, cycle (436 documents) and words. The latest mesh/merge-gate, mesh/repo-check and mesh/delivery on this head are success. mesh-catalog #258 still has one change requested: the two-minute release of an unrecorded question. The fix for it does not change this design text unless the catalogue chooses to cancel such a question. In that case, one sentence here should say so.
mesh-admin merged commit b236b306c4 into main 2026-10-12 21:30:23 +00:00
mesh-admin deleted branch design/589-a-session-asks-the-operator 2026-10-12 21:30:24 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#334