Design 39 bus-and-switch: the lead's answer C5, how a carried switch is read #581

Merged

mesh-tools merged 2 commits from design/39-carried-switches into main 2026-11-12 14:42:06 +00:00

Conversation 1 Commits 2 Files Changed 1

+4

mesh-tools commented 2026-11-12 14:41:07 +00:00

Member

Copy Link

Copy Source

Issue 1409. A switch carried from the old database keeps the old manager's fields (§12); §37's reader answers it with to its licence and consumers its one consumer, and its filters read it the same way; the log is not rewritten (P3, P7). Built by mesh-catalog fix/1409-carried-switches.

Checks: go test ./... at hq's root passes.

Pushed-by: fix-1965@shanks

Issue 1409. A switch carried from the old database keeps the old manager's fields (§12); §37's reader answers it with `to` its licence and `consumers` its one consumer, and its filters read it the same way; the log is not rewritten (P3, P7). Built by mesh-catalog fix/1409-carried-switches. Checks: `go test ./...` at hq's root passes. Pushed-by: fix-1965@shanks

mesh-tools added 2 commits 2026-11-12 14:41:07 +00:00

Design 39 bus-and-switch: the lead's answer C5, how a carried switch is read 8326a3b57d

C5 cites the principles that settle it: failure is loud, the simplest thing 45ee24759b

mesh-tools commented 2026-11-12 14:41:11 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/hq@45ee24759b07 — merged since 2026-11-12T14:42:08Z

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

Transitions

• 2026-11-12 14:41 (new) → proposed (announced): novox/hq#581's head announced
• 2026-11-12 14:41 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-12 14:42 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-delivery:view --> **Delivery** `novox/hq@45ee24759b07` — **merged** since 2026-11-12T14:42:08Z **Source** — source.main moved to novox/hq@63ccbe512bc0. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-12 14:41 (new) → proposed (announced): novox/hq#581's head announced - 2026-11-12 14:41 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-12 14:42 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 63ccbe512b into main 2026-11-12 14:42:06 +00:00

mesh-tools deleted branch design/39-carried-switches 2026-11-12 14:42:07 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#581