To-be 45: the bus module says every user's slow consumer, and S9 raises it (issue 270, ADR 0357) #352

Merged
mesh-admin merged 1 commits from design/270-the-bus-module-says-every-users-slow-consumer into main 2026-10-14 07:00:14 +00:00
Contributor

What

Gives ADR 0357 (accepted) its home in to-be 45:

  • §3 signals table, row S9: a third emitter, the bus module's watch of its server (bus.slow-consumer, bus.connection-closed), and the kind connection-closed, one per bus user.
  • §3 prose: replaces "until the bus has a system account the controller hears a slow consumer and a refused subject for its own connection only" with how every user's slow consumer is heard (30 s watch, said at least once, counted once, read back each tick, clears an hour after the newest; about a minute end to end), and that a refused subject is still heard for the controller's own connection only: the server says it only to the client and in its log (issue 702).
  • §10 Phase 1: mesh-controller and mesh-catalog rows name the new parts.
  • Frontmatter: ADR 0357, updated 2026-10-14.

Why

Issue 270's open question 2. Decided in ADR 0357: the bus module reads its own monitoring endpoint and publishes; no system account (it would not hear refused subjects either), no HTTP from the controller.

Checked

sh merge-check.sh (records, index, cycle, words): pass.

Code: mesh-controller #326 and mesh-catalog #292 (one delivery group, branch fix/270-the-bus-module-says-every-users-slow-consumer).

Relates to issue 270.

## What Gives ADR 0357 (accepted) its home in to-be 45: - §3 signals table, row S9: a third emitter, the bus module's watch of its server (`bus.slow-consumer`, `bus.connection-closed`), and the kind `connection-closed`, one per bus user. - §3 prose: replaces "until the bus has a system account the controller hears a slow consumer and a refused subject for its own connection only" with how every user's slow consumer is heard (30 s watch, said at least once, counted once, read back each tick, clears an hour after the newest; about a minute end to end), and that a refused subject is still heard for the controller's own connection only: the server says it only to the client and in its log (issue 702). - §10 Phase 1: mesh-controller and mesh-catalog rows name the new parts. - Frontmatter: ADR 0357, updated 2026-10-14. ## Why Issue 270's open question 2. Decided in ADR 0357: the bus module reads its own monitoring endpoint and publishes; no system account (it would not hear refused subjects either), no HTTP from the controller. ## Checked `sh merge-check.sh` (records, index, cycle, words): pass. Code: mesh-controller #326 and mesh-catalog #292 (one delivery group, branch fix/270-the-bus-module-says-every-users-slow-consumer). Relates to issue 270.
mesh-admin added 1 commit 2026-10-14 06:43:07 +00:00
Give ADR 0357 a home in design 45: the bus module says every user's slow consumer, and S9 raises it (issue 270)
mesh/merge-gate head bb8075b37bc1 merged into trunk 40a39c860278 — pass: the change touches no module of the mesh's graph
mesh/repo-check head bb8075b37bc1 merged into trunk 40a39c860278 — pass: its merge-check.sh passed
mesh/delivery delivered
bb8075b37b
Author
Contributor

Delivery novox/hq@bb8075b37bc1 — delivered since 2026-10-14T07:00:19Z

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

Transitions

  • 2026-10-14 06:43 (new) → proposed (announced): novox/hq#352's head announced
  • 2026-10-14 06:46 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-14 06:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-14 07:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-14 07:00 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@bb8075b37bc1` — **delivered** since 2026-10-14T07:00:19Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-14 06:43 (new) → proposed (announced): novox/hq#352's head announced - 2026-10-14 06:46 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-14 06:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-14 07:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-14 07:00 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: sound, mergeable at bb8075b37bc1; it states ADR 0357 in to-be 45 and matches mesh-controller #326.

Independent review for issue 270 under ADR 0357.

Checks at this head: mesh/merge-gate success ("PASS — the change touches no module of the mesh's graph"), mesh/repo-check success ("PASS — its merge-check.sh passed"; records, index, cycle and words all pass), mesh/delivery success ("ready: waits for its merge"). No mesh/delivery-group status is set on this head.

  1. The frontmatter adds "ADR 0357" to decisions and sets updated to 2026-10-14. The S9 row now names connection-closed (one per bus user) and the bus module's watch as an emitter. The text describes the watch, the two events, "said at least once, counted once" and the hour read back on each tick, which is what busfaults.go does. Refused subjects for other users are stated as unheard, with issue 702.
  2. The repository table names the controller's read-back and the nats module's watch under mesh-catalog.
  3. No node name, address or credential appears; public-repository rules hold.
  4. One wording point, not blocking: "count each closure once" is true per user and kind. Where the controller's own slow consumer is seen both by its client library and in the server's closure, #326 counts both (see its review).

Ran here, niced: 00-META/checks records.py, index.py, cycle.py and words.py all exit 0.

Reviewed by an independent reviewer on g14.

Verdict: sound, mergeable at bb8075b37bc1; it states ADR 0357 in to-be 45 and matches mesh-controller #326. Independent review for issue 270 under ADR 0357. Checks at this head: mesh/merge-gate success ("PASS — the change touches no module of the mesh's graph"), mesh/repo-check success ("PASS — its merge-check.sh passed"; records, index, cycle and words all pass), mesh/delivery success ("ready: waits for its merge"). No mesh/delivery-group status is set on this head. 1. The frontmatter adds "ADR 0357" to decisions and sets updated to 2026-10-14. The S9 row now names connection-closed (one per bus user) and the bus module's watch as an emitter. The text describes the watch, the two events, "said at least once, counted once" and the hour read back on each tick, which is what busfaults.go does. Refused subjects for other users are stated as unheard, with issue 702. 2. The repository table names the controller's read-back and the nats module's watch under mesh-catalog. 3. No node name, address or credential appears; public-repository rules hold. 4. One wording point, not blocking: "count each closure once" is true per user and kind. Where the controller's own slow consumer is seen both by its client library and in the server's closure, #326 counts both (see its review). Ran here, niced: 00-META/checks records.py, index.py, cycle.py and words.py all exit 0. Reviewed by an independent reviewer on g14.
mesh-admin merged commit dcb5d5ce38 into main 2026-10-14 07:00:14 +00:00
mesh-admin deleted branch design/270-the-bus-module-says-every-users-slow-consumer 2026-10-14 07:00:15 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#352