Issues 326-330: research 036's live bus faults, measured again and diagnosed #217

2026-10-08T14:27:44Z

mesh-admin commented

2026-10-08 14:27:44 +00:00

Registers the live bus faults of research 036 (gap G7) as issues, each measured again read-only through the nats module's tools on 2026-10-08 and diagnosed. No code is changed.

326 (located, not core): mesh-delivery writes a delivery whether or not it changed. keep puts unconditionally and Reconcile passes every walk the controller keeps through it every 30 s; now 1.4 writes/s, about 40/s over the server's life (most of that, I think, issue 313's retries before its fix).
327 (located, core, replay at resolution): every controller verb runs as a fresh process that dials its own bus connection; 41 short connections in 469 s, and 3 conditions calls added 3. The connection total cannot show a reconnect loop.
328 (open, core unknown): 2 JetStream API errors a minute, attributed to nothing; nothing reads the per-call audit advisory. Leads recorded.
329 (located, core, replay at resolution): four <machine>_claude-code event consumers wait for licence events nothing emits; the controller ensures event consumers on every send and never removes one. Proposes the word event consumer.
330 (located, core, replay at resolution): the dead-letter stream design 25 promises does not exist; given-up events are lost after the week EVENTS keeps them.
Issue 270: a dated section records the two server-side slow consumers (both clients on the laptop) under its open question 2, the cause they share.
Research 036's overview points at the issues.

Checks: records, index, cycle and words pass locally (words with the catalogue's list). Do not merge without the operator's approval.

Registers the live bus faults of research 036 (gap G7) as issues, each measured again read-only through the `nats` module's tools on 2026-10-08 and diagnosed. No code is changed. - **326** (located, not core): mesh-delivery writes a delivery whether or not it changed. `keep` puts unconditionally and `Reconcile` passes every walk the controller keeps through it every 30 s; now 1.4 writes/s, about 40/s over the server's life (most of that, I think, issue 313's retries before its fix). - **327** (located, core, replay at resolution): every controller verb runs as a fresh process that dials its own bus connection; 41 short connections in 469 s, and 3 `conditions` calls added 3. The connection total cannot show a reconnect loop. - **328** (open, core unknown): 2 JetStream API errors a minute, attributed to nothing; nothing reads the per-call audit advisory. Leads recorded. - **329** (located, core, replay at resolution): four `<machine>_claude-code` event consumers wait for licence events nothing emits; the controller ensures event consumers on every send and never removes one. Proposes the word *event consumer*. - **330** (located, core, replay at resolution): the dead-letter stream design 25 promises does not exist; given-up events are lost after the week EVENTS keeps them. - **Issue 270**: a dated section records the two server-side slow consumers (both clients on the laptop) under its open question 2, the cause they share. - Research 036's overview points at the issues. Checks: records, index, cycle and words pass locally (words with the catalogue's list). Do not merge without the operator's approval.

mesh-admin added 1 commit 2026-10-08 14:27:44 +00:00

Issues 326-330: register research 036's live bus faults, each diagnosed

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

c64a7b3d4a

The bus's own numbers were unexplained and raised by nothing. Measured again
read-only: mesh-delivery rewrites unchanged deliveries (326), every controller
verb dials its own connection (327), API errors have no reader (328), event
consumers outlive their declaration (329), and design 25's dead-letter stream
was never built (330). The two slow consumers join issue 270, whose missing
system account they share.

mesh-admin commented

2026-10-08 14:28:02 +00:00

Delivery novox/hq@c64a7b3d4a47 — delivered since 2026-10-08T14:29:28Z

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

Transitions

2026-10-08 14:27 (new) → proposed (announced): novox/hq#217's head announced
2026-10-08 14:28 proposed → checked (checked): the verdict names this commit
2026-10-08 14:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 14:29 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 14:29 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.

**Delivery** `novox/hq@c64a7b3d4a47` — **delivered** since 2026-10-08T14:29:28Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 14:27 (new) → proposed (announced): novox/hq#217's head announced - 2026-10-08 14:28 proposed → checked (checked): the verdict names this commit - 2026-10-08 14:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 14:29 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 14:29 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 merged commit 1782f1ad74 into main

2026-10-08 14:29:18 +00:00

mesh-admin deleted branch issues/036-bus-faults

2026-10-08 14:29:18 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#217