mesh-delivery: say which order rule won, and how to end a contradiction (hq issue 309) #119

2026-10-08T08:45:38Z

mesh-admin commented

2026-10-08 08:45:38 +00:00

A group whose order rules disagreed was refused as "its order contradicts itself: " — nobody could see which rules clashed or what to write.

The controller now answers, per pair, over (the rules it won over by precedence, hq ADR 0249) and contradictions (equal-rank rules both ways, with both rules and how to declare the order). mesh-delivery keeps both on the group, lists them in groups, prints them in the plan note ("A before B: built by, over engine before controller"), and refuses a group by the contradiction's words. A cycle through more members names the pairs in it. An older controller's answer (no new fields) reads as before.

Tests: TestAGroupSaysWhichOrderRuleWonOrWhyNoneDid, TestACycleWithoutAContradictionNamesItsPairs. merge-check.sh passes with the changed files given (no controller built beside it locally, so the manifest step said NOT CHECKED).

Merge after novox/mesh-controller's PR for 309.

A group whose order rules disagreed was refused as "its order contradicts itself: <ids>" — nobody could see which rules clashed or what to write. The controller now answers, per pair, `over` (the rules it won over by precedence, hq ADR 0249) and `contradictions` (equal-rank rules both ways, with both rules and how to declare the order). mesh-delivery keeps both on the group, lists them in `groups`, prints them in the plan note ("A before B: built by, over engine before controller"), and refuses a group by the contradiction's words. A cycle through more members names the pairs in it. An older controller's answer (no new fields) reads as before. Tests: `TestAGroupSaysWhichOrderRuleWonOrWhyNoneDid`, `TestACycleWithoutAContradictionNamesItsPairs`. `merge-check.sh` passes with the changed files given (no controller built beside it locally, so the manifest step said NOT CHECKED). Merge after novox/mesh-controller's PR for 309.

mesh-admin added 1 commit 2026-10-08 08:45:38 +00:00

Say which order rule won, and how to end a contradiction (hq issue 309)

mesh/delivery delivered

Details

mesh/merge-gate pass: builds mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

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

Details

6ae112d299

A group whose order rules disagreed was refused as "its order contradicts
itself" with only the member ids: nobody could see which rules clashed or
what to write to resolve it. The controller now resolves rules by
precedence (hq ADR 0249) and answers, per pair, the rules it won over, and
per contradiction no precedence resolves, both rules and how to declare
the order. mesh-delivery keeps both, lists them in groups and the plan
note, and refuses a group by those words; a cycle through more members
names the pairs in it. An older controller's answer reads as before.

mesh-admin commented

2026-10-08 08:48:44 +00:00

Delivery novox/mesh-catalog@6ae112d299d5 — delivered since 2026-10-08T09:15:18Z

Delivery plan — builds mesh-delivery → novox; no bus step

tier 0: mesh-delivery
novox: receives mesh-delivery

Machines

mesh-delivery on novox: passed — healthy 3 times over 2m59s
mesh-delivery on the rest running it: sent

Transitions

2026-10-08 08:48 (new) → proposed (announced): novox/mesh-catalog#119's head announced
2026-10-08 08:52 proposed → checked (checked): the verdict names this commit
2026-10-08 08:52 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 09:11 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 09:11 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-08 09:15 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@6ae112d299d5` — **delivered** since 2026-10-08T09:15:18Z **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery **Machines** - mesh-delivery on novox: passed — healthy 3 times over 2m59s - mesh-delivery on the rest running it: sent **Transitions** - 2026-10-08 08:48 (new) → proposed (announced): novox/mesh-catalog#119's head announced - 2026-10-08 08:52 proposed → checked (checked): the verdict names this commit - 2026-10-08 08:52 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 09:11 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 09:11 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-08 09:15 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin commented

2026-10-08 08:52:35 +00:00

Merge check at 6ae112d2

mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery)
mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds mesh-delivery → novox; no bus step

tier 0: mesh-delivery
novox: receives mesh-delivery

Run by the build seat on novox as build-1791449290204057311 (builds --log build-1791449290204057311).

--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, keeps state deliveries, groups
long-running resources without health: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T08:44:32Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-08T08:44:32Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-delivery
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 28304 strings of 524 files
long-running resources without health: 70, as kept
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	1.139s

**Merge check** at `6ae112d2` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery Run by the build seat on novox as `build-1791449290204057311` (`builds --log build-1791449290204057311`). ``` --- the gate: mesh-delivery mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, keeps state deliveries, groups long-running resources without health: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T08:44:32Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-08T08:44:32Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-delivery --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 28304 strings of 524 files long-running resources without health: 70, as kept testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 1.139s ```

mesh-admin merged commit 3d15c71fab into main

2026-10-08 09:11:26 +00:00

mesh-admin deleted branch fix/309-a-group-says-which-order-rule-won

2026-10-08 09:11:27 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#119