R6: the assigner writes wants by rule 7 with the composition digest; the watchman and the view follow wants and haves (issue 1906) #38

2026-10-24T22:17:08Z

mesh-tools commented

2026-10-24 22:17:08 +00:00

The assigner brings what release 5 left out (issue 1906): wants for every module, the node key's want, rule 7 and the composition digest in the want, the restore ask for a data module, the condition for a held fingerprint, acting on the release answer, policy record from the controller's judgement, and the backup answer in the want. The watchman mirrors wants as pulses the node agent owes; the view reads wants and haves and shows a source revision as delivered. Main's composer (the R4g finish) is kept beside it: the assigner still reads the controller's build records for it.

Tries: try-1792877834591158107 passed on 3e863884.

Delivery group feat/r6 (design 47, milestone R6; ADR 0539, ADR 0540): mesh-sdk, mesh-host, mesh-delivery, mesh-catalog, hq, mesh-controller. One Approve for the group; its delivery is the last delivery plan the controller runs, and after it a merged change reaches each machine through its wants alone.

After the delivery: the operator's signing key is set as mesh-host's operator-signers setting, and acceptance test 18 is read live.

Release-switch: 6
Reviewed-by: reviewer-r6m@shanks at 3e863884fd
Pushed-by: lead-47@shanks

The assigner brings what release 5 left out (issue 1906): wants for every module, the node key's want, rule 7 and the composition digest in the want, the restore ask for a data module, the condition for a held fingerprint, acting on the release answer, policy `record` from the controller's judgement, and the backup answer in the want. The watchman mirrors wants as pulses the node agent owes; the view reads wants and haves and shows a source revision as delivered. Main's composer (the R4g finish) is kept beside it: the assigner still reads the controller's build records for it. Tries: try-1792877834591158107 passed on 3e863884. Delivery group feat/r6 (design 47, milestone R6; ADR 0539, ADR 0540): mesh-sdk, mesh-host, mesh-delivery, mesh-catalog, hq, mesh-controller. One Approve for the group; its delivery is the last delivery plan the controller runs, and after it a merged change reaches each machine through its wants alone. After the delivery: the operator's signing key is set as mesh-host's operator-signers setting, and acceptance test 18 is read live. Release-switch: 6 Reviewed-by: reviewer-r6m@shanks at 3e863884fda8487282868a2fe9f13ba15d916687 Pushed-by: lead-47@shanks

mesh-tools added 31 commits 2026-10-24 22:17:08 +00:00

Read the assigner's wants, differences and the haves with tools, so the gap between wants and sends can be read live (issue 1906 D1) 4fd6b934c8

End the assigner's comparison with the send: the controller sends nothing to compare with, so the differences bucket is kept read-only (issue 1906 D5, ADR 0539 §8) 024a3787da

The watchman mirrors each want of the assigner as a pulse owed by the node's agent until the have names its fingerprint (issue 1906 D6) 9d2e9dc6c9

The view shows each want beside the have of its node, and a source revision's derived state, in place of the comparison with sends (issue 1906 D7) f048e2b443

The assigner asks whether to restore a data module whose held fingerprint failed its health check, and raises the condition for a held fingerprint (issue 1906 D3) 204a59dab4

Give the data module's test manifest the directory and backup the catalogue asks of an irreplaceable item 7b18696cd5

Prove the assigner replaced mid-pass resumes with nothing lost or written again (issue 1906 D8) 12b01badb0

Pin the assigner, watchman and view to mesh-sdk's release 6 head (issue 1943 S3) and give their test wants a composition digest 806c8bf0e4

The assigner's seventh rule: a want names the digest of its composition and waits for it; a revision at the same fingerprint is a new want; the node's own want (issue 1906 D2, ADR 0539 §6) 0df20b5d77

The assigner acts on answers: a release writes the held want again, a backup answer goes into the node's want, a record move waits for its yes, a restore answer sets a data module back (issue 1906 D4) 04c2c60f02

The view shows the controller's judgement of the move beside each want (issue 1906 D7, ADR 0539 §14) f947070b7b

The record policy is the one the controller holds beside the composition, the operator's own choice included; pin mesh-sdk 64a502d (issue 1906 D4, ADR 0539 §14) e7a3ff1e7e

Do not wait twice at the cleanup for an assigner that ended on its own, which made the refused-start test take ten seconds a bucket 55f19283f4

A node that runs a module of policy record with no want yet is asked like any other, not treated as one that never ran it (issue 1906 D4) 37a5ab8f1c

The view says its event delivered once for each source revision whose wants and haves are all there (issue 1906 D9, for issue 1946) 86fd0bbe96

Let the view's manifest test read the emits key the delivered event adds 37d0ebba7a

Merge remote-tracking branch 'origin/main' into feat/r6 03e5951dc5

The checker reads a kept manifest as the indexer and the assigner do, so a value falling back to a predefined key is not logged unreadable (issue 1906, issues 1751 and 1921 class) 333e0cd07d

Pin the assigner, watchman and view to the head of mesh-sdk feat/r6 (issue 1943) 14c20b21ee

Review round 1: the bus with no want is compared with its have; a backup ask is bound to its composition and number and each answer is a distinct want value; the view reads wants and haves, with dotted module names (issue 1906) fcac03a4f2

Review round 1: a user-list-only revision of the bus is written at once at the fingerprint it runs, before the record hold; pin mesh-sdk a523a8c (issue 1906) 3b00f3890d

Start the world's change counter, which the pass of a held backup reads (issue 1906, review round 1) 8280506cee

The view says modules in motion: moving, settled and stuck, once for a node, a module and a composition (issue 1906 D10, for the messenger) a3815051cc

The view's motion events carry the time they are about and call a held or past-bound module stopped, as the messenger reads them (issue 1906 D10) da31740f00

Pin the assigner, watchman and view to mesh-sdk feat/r6 e45bdc0 (issue 1943) 0f7bc9f531

Right after the switch a node running F with a have that names no composition is given its want at F with no record hold, the bus included (issue 1906, review round 2 N1) e263049551

Pin the assigner, watchman and view to mesh-sdk feat/r6 7f9cc0e (issue 1943) 9a5b3d4881

The switch exception skips the record hold only for a composition the controller judges unchanged; pin mesh-sdk d7a9b96 (issue 1906, ADR 0540 §9) 36a1fd197f

Merge main into feat/r6: keep R4g's composer at a group's mesh-sdk head beside R6's wants and asks aa31e85665

The assigner reads mesh-controller.builds again (the composer's runningCommits reads the build record of every open
assignment), puts its compose asks on node-build-go and says its conditions on operator-channel.

Pin mesh-sdk to feat/r6 748c564, which carries main's composer (issue 1943) c21bed20a3

gofmt the passer's fields after main's merge

mesh/delivery-group group feat/r6 merged: every member is merged

Details

mesh/delivery delivering: 0 machine step(s) passed

Details

mesh/check checking 3e863884fda8 on 650a06ceab1d | novox/mesh-delivery#38 in group feat/r6

3e863884fd

mesh-tools commented

2026-10-24 22:17:11 +00:00

Delivery novox/mesh-delivery@3e863884fda8 — delivering since 2026-10-24T23:19:25Z

Delivery plan — builds mesh-delivery-assigner, mesh-delivery-checker, mesh-delivery-view, mesh-delivery-watchman → ace, novox, shanks; no bus step

tier 0: mesh-delivery-assigner, mesh-delivery-checker, mesh-delivery-view, mesh-delivery-watchman
ace: receives mesh-delivery-assigner
novox: receives mesh-delivery-checker, mesh-delivery-watchman
shanks: receives mesh-delivery-view
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-delivery-assigner, mesh-delivery-view is judged on its first machine

Group feat/r6: novox/hq@ba09497092, novox/mesh-catalog@d09cbf1523, novox/mesh-controller@9c38aed789, novox/mesh-delivery@3e863884fd, novox/mesh-host@81758b24a8, novox/mesh-sdk@748c564cdf

composed together: pass — the checker's verdict at the members' heads (d2bc2f317716)

Transitions

2026-10-24 22:17 (new) → proposed (announced): novox/mesh-delivery#38's head announced
2026-10-24 22:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-24 22:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-24 23:19 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-24 23:19 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

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

**Delivery** `novox/mesh-delivery@3e863884fda8` — **delivering** since 2026-10-24T23:19:25Z **Delivery plan** — builds mesh-delivery-assigner, mesh-delivery-checker, mesh-delivery-view, mesh-delivery-watchman → ace, novox, shanks; no bus step - tier 0: mesh-delivery-assigner, mesh-delivery-checker, mesh-delivery-view, mesh-delivery-watchman - ace: receives mesh-delivery-assigner - novox: receives mesh-delivery-checker, mesh-delivery-watchman - shanks: receives mesh-delivery-view - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-delivery-assigner, mesh-delivery-view is judged on its first machine **Group** `feat/r6`: novox/hq@ba09497092ec, novox/mesh-catalog@d09cbf152317, novox/mesh-controller@9c38aed78905, novox/mesh-delivery@3e863884fda8, novox/mesh-host@81758b24a8e4, novox/mesh-sdk@748c564cdf7c - composed together: pass — the checker's verdict at the members' heads (d2bc2f317716) **Transitions** - 2026-10-24 22:17 (new) → proposed (announced): novox/mesh-delivery#38's head announced - 2026-10-24 22:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-24 22:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-24 23:19 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-24 23:19 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 The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben merged commit 650a06ceab into main

2026-10-24 23:17:46 +00:00

jschoubben deleted branch feat/r6

2026-10-24 23:17:47 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#38