novox/mesh-catalog
13
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

The router takes a module's condition on the operator channel's one subject (design 47 R3b: issues 1217, 1218) #369

Merged
mesh-tools merged 5 commits from feat/delivery-seat-by-claim into main 2026-10-19 10:28:29 +00:00
Conversation 1 Commits 5 Files Changed 11
+465 -45
mesh-tools commented 2026-10-19 10:17:45 +00:00
Member
Copy Link
Copy Source

Design 47 milestone R3b (ADR 0437 §9), one delivery group with mesh-controller's feat/delivery-seat-by-claim. The operator sees no change in R3b.

  • issue 1217: the router (messenger) takes a module's condition on mesh.seat.operator-channel.accept.condition., in mesh-sdk's layout, and decides its channels as for the controller's conditions; the seat operator-channel declares condition among its accepts and by-caller verbs; a module's condition is never ended by the sync with the controller's conditions (1217/AC7). mesh-sdk pinned at main aa68b673 (which moves go to 1.26.0).
  • issue 1218: bus tests: a condition said on the subject reaches the desk and is cleared; a warning that needs nothing reaches no channel. The router's start grace and burst window are vars, shortened in the test bundle only.

Tests from each issue's acceptance criteria. Review: 2 rounds and one cycle after a failed try (the burst window held the tests' warnings 30 s). Try build-1792404961076653401 passed (1m15s).

Reviewed-by: reviewer-r3b@shanks at 5aca005cb7

Design 47 milestone R3b (ADR 0437 §9), one delivery group with mesh-controller's feat/delivery-seat-by-claim. The operator sees no change in R3b. - issue 1217: the router (messenger) takes a module's condition on mesh.seat.operator-channel.accept.condition.<publisher>, in mesh-sdk's layout, and decides its channels as for the controller's conditions; the seat operator-channel declares condition among its accepts and by-caller verbs; a module's condition is never ended by the sync with the controller's conditions (1217/AC7). mesh-sdk pinned at main aa68b673 (which moves go to 1.26.0). - issue 1218: bus tests: a condition said on the subject reaches the desk and is cleared; a warning that needs nothing reaches no channel. The router's start grace and burst window are vars, shortened in the test bundle only. Tests from each issue's acceptance criteria. Review: 2 rounds and one cycle after a failed try (the burst window held the tests' warnings 30 s). Try build-1792404961076653401 passed (1m15s). Reviewed-by: reviewer-r3b@shanks at 5aca005cb741306fbe2caece689c3330fa124e02
mesh-tools added 5 commits 2026-10-19 10:17:46 +00:00
Take a module's condition on the operator channel's one subject (issue 1217) de6741a335
Prove over the bus that a condition on the one subject reaches the desk (issue 1218) 5b235a6e80
Keep a module's condition open when the controller's conditions are read (issue 1217, review round 1 finding 1) f737418bb3
Shorten the router's start grace in the test bundle so the bus tests stay in seconds (issue 1218, review round 1 finding 2) 9f9e9fc9d3
Shorten the router's burst window in the test bundle so the desk is sent within seconds (issue 1218, check finding 1)
mesh/repo-check head 5aca005cb741 merged into trunk b4527d9091e9 beside mesh-controller#394@3e7f34d0 — pass: its merge-check.sh passed, each part in its to…
Details
mesh/merge-gate head 5aca005cb741 merged into trunk b4527d9091e9 — pass: group feat/delivery-seat-by-claim composed: every machine composes with the change…
Details
mesh/delivery delivered
Details
mesh/delivery-group group feat/delivery-seat-by-claim delivered: every member is delivered
Details
5aca005cb7
mesh-tools commented 2026-10-19 10:17:52 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@5aca005cb741 — delivered since 2026-10-19T10:39:55Z

Delivery plan — builds messenger → novox; no bus step

  • tier 0: messenger
  • novox: receives messenger

Group feat/delivery-seat-by-claim: novox/mesh-catalog@5aca005cb7, novox/mesh-controller@3e7f34d041

  • composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Machines

  • mesh-controller on every machine running it: sent
  • route-proxy on every machine running it: sent
  • build-agent on every machine running it: sent
  • messenger on every machine running it: sent

Transitions

  • 2026-10-19 10:17 (new) → proposed (announced): novox/mesh-catalog#369's head announced
  • 2026-10-19 10:18 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-19 10:18 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-19 10:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-19 10:30 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-19 10:39 delivering → delivered (done): its walk is done, carrying its own commit: 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-delivery:view --> **Delivery** `novox/mesh-catalog@5aca005cb741` — **delivered** since 2026-10-19T10:39:55Z **Delivery plan** — builds messenger → novox; no bus step - tier 0: messenger - novox: receives messenger **Group** `feat/delivery-seat-by-claim`: novox/mesh-catalog@5aca005cb741, novox/mesh-controller@3e7f34d041b1 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-controller on every machine running it: sent - route-proxy on every machine running it: sent - build-agent on every machine running it: sent - messenger on every machine running it: sent **Transitions** - 2026-10-19 10:17 (new) → proposed (announced): novox/mesh-catalog#369's head announced - 2026-10-19 10:18 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-19 10:18 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-19 10:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-19 10:30 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-19 10:39 delivering → delivered (done): its walk is done, carrying its own commit: 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-tools merged commit fb8e677cd8 into main 2026-10-19 10:28:29 +00:00
mesh-tools deleted branch feat/delivery-seat-by-claim 2026-10-19 10:28:29 +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
Projects
Clear projects
No projects
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#369