Design 47 G: A-352, a bus module's running build counts while its newer build waits for the operator's yes #606

2026-11-13T12:09:52Z

mesh-tools commented

2026-11-13 12:09:52 +00:00

The lead's answer A-352 (ADR 0614 §5 and §2; principle 3). The second dry run read this from the mesh on 2026-11-13: nats's new build on novox waits for the operator's yes, and its old build still runs. The assigner's bus-state rule counts only a running, healthy build, so it holds every bus-state consumer (zfs on ace now). ADR 0614 §5 asks for "a build of the bus module that offers bus-state runs healthy", which the running build is. A consumer that needs a form only the new build reads still waits by its kind-4 edge (§50).

Checked: go test ./00-META/checks/ passes.

https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

The lead's answer A-352 (ADR 0614 §5 and §2; principle 3). The second dry run read this from the mesh on 2026-11-13: nats's new build on novox waits for the operator's yes, and its old build still runs. The assigner's bus-state rule counts only a running, healthy build, so it holds every bus-state consumer (zfs on ace now). ADR 0614 §5 asks for "a build of the bus module that offers bus-state runs healthy", which the running build is. A consumer that needs a form only the new build reads still waits by its kind-4 edge (§50). Checked: `go test ./00-META/checks/` passes. https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

mesh-tools added 1 commit 2026-11-13 12:09:52 +00:00

Answer A-352: a bus module's running build counts while its newer build waits for the operator's yes

mesh/delivery merged: source.main moved to novox/hq@0bbcf98baa96

Details

mesh/check checking 328ca1b32047 on 0bbcf98baa96

328ca1b320

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

mesh-tools commented

2026-11-13 12:09:55 +00:00

Delivery novox/hq@328ca1b32047 — merged since 2026-11-13T12:10:54Z

Source — source.main moved to novox/hq@0bbcf98baa. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-13 12:09 (new) → proposed (announced): novox/hq#606's head announced
2026-11-13 12:09 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-13 12:10 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/hq@328ca1b32047` — **merged** since 2026-11-13T12:10:54Z **Source** — source.main moved to novox/hq@0bbcf98baa96. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-13 12:09 (new) → proposed (announced): novox/hq#606's head announced - 2026-11-13 12:09 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-13 12:10 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 0bbcf98baa into main

2026-11-13 12:10:51 +00:00

mesh-tools deleted branch design/47-G-lead-answers-29

2026-11-13 12:10:51 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#606