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.
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).
Deliverynovox/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`.
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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).
Delivery
novox/hq@f7c677a3a712— delivered since 2026-10-12T21:30:52ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: approve at
a5333f8ecbIndependent review of to-be 46's new section "An agent session asks" against ADR 0332 (accepted, version 8), issue 589.
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
f7c677a3a7Re-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.