R4e (mesh-controller): deliver from the builder's keys, ask build-agent only for its own modules, follow the forge's protection for checks, announce the controller's states #441

2026-10-22T21:51:43Z

mesh-tools commented

2026-10-22 21:51:43 +00:00

Delivery group feat/r4e (R4e of design 47: ADR 0503, 0513, 0514, 0520, 0521; ADR 0498, 0501). Members: mesh-sdk, mesh-controller, mesh-delivery, mesh-catalog, all on branch feat/r4e.

This member: a delivery plan takes its modules from the builder's done keys and asks build-agent only for its own modules until R4g (the builder's module, build-agent and mesh-tools, ADR 0520; issue 1851); new modules are registered from their first done key; the terminal's build/rebuild/replay --register are removed, register and switch added (C3); pull request checks follow the trunk's protection, mesh/repo-check still asked of build-agent where the trunk requires it, hq included (ADR 0513 §4; issues 1299, 1318; C2); the controller announces its states (ADR 0495, issue 1790); a starting controller sends the bus machine its user list before anything writes its buckets (issue 1800); a retry names the modules still waiting for the bus (issue 1403); mesh-sdk pinned at the group's head 104533e8 and re-vendored.

Tests: unit suite and the whole integration level; try PASS on d51324df (build-1792697129298002967).

Reviewed-by: review-r4e@shanks at d51324df45

Delivery group feat/r4e (R4e of design 47: ADR 0503, 0513, 0514, 0520, 0521; ADR 0498, 0501). Members: mesh-sdk, mesh-controller, mesh-delivery, mesh-catalog, all on branch feat/r4e. This member: a delivery plan takes its modules from the builder's done keys and asks build-agent only for its own modules until R4g (the builder's module, build-agent and mesh-tools, ADR 0520; issue 1851); new modules are registered from their first done key; the terminal's build/rebuild/replay --register are removed, register and switch added (C3); pull request checks follow the trunk's protection, mesh/repo-check still asked of build-agent where the trunk requires it, hq included (ADR 0513 §4; issues 1299, 1318; C2); the controller announces its states (ADR 0495, issue 1790); a starting controller sends the bus machine its user list before anything writes its buckets (issue 1800); a retry names the modules still waiting for the bus (issue 1403); mesh-sdk pinned at the group's head 104533e8 and re-vendored. Tests: unit suite and the whole integration level; try PASS on d51324df (build-1792697129298002967). Reviewed-by: review-r4e@shanks at d51324df45184e049757436d7795e43237590a9e

mesh-tools added 39 commits 2026-10-22 21:51:43 +00:00

Read the builder's keys, the indexer's values by commit and its manifests, so the controller can take a module from a done key (issue 1851, A1, A2) 1ed7e34155

Vendor the R4e mesh-sdk member's head for its shared launcher rule and the manifest word paths (issue 1851; re-pinned to the final head in E) eff0d5cbf4

Judge a recorded build, not build-agent's outcome, and read a registration's warrant from the merge a key names, so a done key registers under the same rules (issue 1851, A4a) f00b6aff8b

Take a module in from the builder's done key of its trunk fingerprint: one record of the key's artifacts, its manifest judged against the catalogue trunk's predefined keys (issue 1851, A3, A4b, A4c) d984f0a55d

Register a new module from the builder's first done key and ask no first build; its condition reads the key and names a manifest word this controller does not read (issue 1851, A5a, A5b) ea3c8ad7f6

Take a walk's modules from the builder's done keys and ask no build but the builder's own: a key building or unreferenced holds the tier and says so, a failed key fails the walk in its words (issue 1851, A6, A7) 62268cf43d

Delete the walk's reuse of a check's build: a walk takes keys and asks build-agent only for the builder's own module (issue 1851, A8) 7743bd0d4b

Move no module whose fingerprint is unchanged, and let a key's build stand on the held build-agent build of the same digests at the switch (issue 1851, A9) 9da79ef8c3

Keep an assignment of a module whose key is coming pending on that key and ask no build; nothing asks a request again at start (issue 1851, A10) 0aec975d19

Mark the walks the integration tests drive around the one ask left as the builder's own, and expect no ask of a moved module (issue 1851, A5, A6) 7f6d418205

Ask the checker for a try of a branch head, not build-agent, and read its word in today's answer (issue 1851, A11, ADR 0501 §5) f76da2ce9c

Refuse build, rebuild and replay --register by name, naming what replaced them, and delete the hand builds (issue 1851, A11a, ADR 0501 §5) c7039d81e1

Register a module from a repository the catalogue does not build at the controller's terminal alone, from its done trunk key, naming exactly its repository and path (issue 1851, A11b, ADR 0501 §4) b71425867f

Refuse, in the one function every ask goes through, an ask of build-agent for any module but the builder's own (issue 1851, A12, ADR 0453 §5) 1963d84a7a

Name, before the switch, which modules it moves: the held build's digests against the builder's done key, images and packages said as what cannot be compared (issue 1851, A13) a8387ebad8

Read a module whose every artifact names its paths from those paths and its manifest alone, so a change elsewhere in its directory moves nothing (issue 1758, B1, ADR 0499 §5) e7e23c57cc

Ask no pull request check of build-agent but the own merge-check.sh of a repository whose trunk requires mesh/repo-check alone, and say every verdict with no gate layer (issue 1299, C1, ADR 0503 §3, §5) 323e1270cc

Read a commit as the same as itself however short, and fit the pending assignments' tests to a mesh that asks no build (issue 1851, A9, A10) 25fdf9920e

Ask build-agent no composed check of a delivery group, and answer that the checker judges it (issue 1299, C2, ADR 0503 §3) 3a1937914e

Refuse delivery-plan and forget-checks by name and take a merge's warrant from the teller alone, no longer mesh-delivery's (issue 1318, C3, ADR 0450 §8) 45d091778c

Vendor the R4e mesh-sdk member's head with the states announcement (issue 1790; re-pinned to the final head in E) b6ed18197b

Announce the controller's states, keep every module's word, and grant a read only where its owner announced the state readable; the copied list of the controller's mirrors goes (issue 1790, D1-D4, ADR 0495, ADR 0513 §3) d36e0ea278

Refuse a removed verb by name before reading its arguments, as the SDK member's table now offers none (issue 1851, A11a; issue 1318, C3) 791c2a3d48

Say again what the controller keeps at every push, so a word refused before its grant is kept once a push carries it (issue 1790, D1) ab33f015ec

Take a walk's key in again when it was recorded at an earlier merge, so the module is registered at the commit the walk carries before it is built (issue 1851, A6) dfc2f2aa98

Vendor what go.mod pins after the rebase on main (issue 1790; the SDK's 1833 fix returns with E's re-pin) a10ef8995b

Serve a removed verb as its refusal, not as a verb this build is behind on, and fit the tests of the verbs and the stopped checks (issue 1851, A11a; issue 1299, C1; issue 1318, C3) 7c0e1d223f

Test the group check's answer without swapping standard output, and wait for a take-in to forget a new module's wait (issue 1299, C2; issue 1851, A5) 420ae3d0e7

Count the work the take-ins start in the background, so a test's mesh closes only once that work has ended (issue 1851, A5-A7; issue 1790, D3) bc80683b9e

Merge main (upgrade safety's declared packages, issue 1840) and pin the R4e mesh-sdk member's final head 875c680d, re-vendored here and in modules/route-proxy; the controller announces declared-packages readable (issue 1790, D1; E) a0b2d98002

Send the bus its user list before a starting controller writes (issue 1800) d5d53893a4

A new controller's grants reached the bus only after its gate, so the
buckets it newly writes were refused until then. At start it now sends
the bus's machine the user list alone, every build there kept.

Name a retry's modules still waiting for the bus, read as the plan it resumes (issue 1851 A11a, issue 1403) 93fc2f48a1

With the hand rebuild gone, a retry of a plan failed past the bus's bound
read the waiting modules while the plan still said failed, named none,
and answered "asked" with nothing after it.

Ask build-agent for itself and its toolchain images, never a builder key (ADR 0520, issue 1851) 9713ceb84d

The builder writes no key of build-agent or of the toolchain bases its
builds stand on, so a walk moving one would hold its tier for ever.
Until R4g they are build-agent's own, as the builder's module is; the
bases are read from the toolchains, not copied.

Ask a repository check whenever the trunk requires it, beside mesh/check (issue 1299 C1, ADR 0513 §4) 61f7e89ad5

A trunk requiring both contexts (hq) matched mesh/check first and had
its own merge-check.sh never asked.

Name build-agent's own as the builder's module, build-agent and mesh-tools (ADR 0520 §1, issue 1851) 61449249a8

ADR 0520 narrowed after its review: mesh-tools-go builds from its own
directory on a pinned base and has its key from mesh-build-image, and
mesh-tools-python is no module, so the set is named, not derived from
the toolchain bases.

List register and switch in the help, and none of the removed commands (issue 1851 A11a, A11b) f9014452d3

The help still offered build, rebuild and replay --register, each now
refused as removed, and did not name the terminal's register.

List the store tests R4e adds, and drop those of the hand builds and the stopped checks it deleted (issue 1851, issue 1299) 1fd833bfe8

The merge check refused the eight deleted tests as listed and not run.

Pin mesh-sdk at the R4e member's final head 104533e8 and vendor it (R4e E) 58512a9c6d

The SDK's S1 and S2 review fixes landed after 875c680d.

Format the help's test (issue 1851)

mesh/repo-check head d51324df4518 merged into trunk f2a4363a1a77 beside mesh-catalog#457@896bd883 — pass: its merge-check.sh passed

Details

mesh/merge-gate head d51324df4518 merged into trunk f2a4363a1a77 — pass: group feat/r4e composed: every machine composes with the change as it did without …

Details

mesh/check failed: unit: ..test: node:internal/modules/esm/resolve:989 | d51324df4518 on f2a4363a1a77 | unit 1 run, 0 kept | integration 0 run, 0 kept…

mesh/delivery covered after its stop: a later walk that contains it was delivered: plan-1792707174627079192 (novox/mesh-controller at 289bbf68 into main,…

Details

mesh/delivery-group group feat/r4e delivered: every member is delivered

Details

d51324df45

mesh-tools commented

2026-10-22 21:52:16 +00:00

Delivery novox/mesh-controller@d51324df4518 — stopped since 2026-10-23T00:01:53Z

Covered: covered after its stop: a later walk that contains it was delivered: plan-1792707174627079192 (novox/mesh-controller at 289bbf68 into main, done, contains its merge 289bbf68)

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

tier 0: mesh-controller, route-proxy
tier 1: build-agent
ace: receives route-proxy, build-agent
g14: receives build-agent
novox: receives mesh-controller, route-proxy, build-agent
shanks: receives build-agent
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
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 route-proxy, build-agent is judged on its first machine

Group feat/r4e: novox/mesh-catalog@896bd88380, novox/mesh-controller@d51324df45, novox/mesh-delivery@efca168c55, novox/mesh-sdk@22b70c82b0

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
mesh-sdk on every machine running it: sent
pacman on every machine running it: sent
route-proxy on every machine running it: sent
build-agent on every machine running it: sent
mesh-build-go on every machine running it: sent
mesh-build-image on every machine running it: sent
mesh-build-node on every machine running it: sent
mesh-delivery-checker on every machine running it: sent
mesh-delivery-forge-bridge on every machine running it: sent
mesh-delivery-gate on every machine running it: sent
mesh-delivery-indexer on every machine running it: sent
mesh-delivery-view on every machine running it: sent
mesh-tools on every machine running it: sent
audit-logger on every machine running it: sent
baserow on every machine running it: sent
bazarr on every machine running it: sent
bookshelf on every machine running it: sent
confluence on every machine running it: sent
gitea on every machine running it: sent
gitlab on every machine running it: sent
grafana on every machine running it: sent
home-assistant on every machine running it: sent
icecast on every machine running it: sent
influxdb on every machine running it: sent
jackett on every machine running it: sent
jira on every machine running it: sent
kometa on every machine running it: sent
lab on every machine running it: sent
letta on every machine running it: sent
lidarr on every machine running it: sent
mailu on every machine running it: sent
mesh-catalog on every machine running it: sent
mesh-delivery-builder on every machine running it: sent
minio on every machine running it: sent
model-usage on every machine running it: sent
mongodb on every machine running it: sent
mosquitto on every machine running it: sent
mssql on every machine running it: sent
netcheck on every machine running it: sent
nextcloud on every machine running it: sent
nodered on every machine running it: sent
ombi on every machine running it: sent
openai-consumer on every machine running it: sent
radarr on every machine running it: sent
redis on every machine running it: sent
route-adapter on every machine running it: sent
searxng on every machine running it: sent
showcase on every machine running it: sent
sonarr on every machine running it: sent
tautulli on every machine running it: sent
umami on every machine running it: sent
unifi on every machine running it: sent
zsh on every machine running it: sent

Transitions

2026-10-22 21:52 (new) → proposed (announced): novox/mesh-controller#441's head announced
2026-10-22 22:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-22 22:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-22 22:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-22 22:15 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-23 00:01 delivering → stopped (stop): its walk plan-1792707174627079192 was stopped by a person (mesh-controller): issue 1886 (the operator, 02:08: fix it right now): stuck for good on builder keys nothing running can reference; as an open plan it holds every merge check, including the fix mesh-controller #442. The fixed controller goes to novox by the bootstrap act (ADR 0522 §5); R4e's 8 + 40 remaining modules are carried on afterwards by a retry that resumes a hand-stopped plan (follow-up on issue 1886, note 7).

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

**Delivery** `novox/mesh-controller@d51324df4518` — **stopped** since 2026-10-23T00:01:53Z **Covered**: covered after its stop: a later walk that contains it was delivered: plan-1792707174627079192 (novox/mesh-controller at 289bbf68 into main, done, contains its merge 289bbf68) **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller, route-proxy - tier 1: build-agent - ace: receives route-proxy, build-agent - g14: receives build-agent - novox: receives mesh-controller, route-proxy, build-agent - shanks: receives build-agent - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - 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 route-proxy, build-agent is judged on its first machine **Group** `feat/r4e`: novox/mesh-catalog@896bd88380b3, novox/mesh-controller@d51324df4518, novox/mesh-delivery@efca168c5522, novox/mesh-sdk@22b70c82b0ab - 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 - mesh-sdk on every machine running it: sent - pacman on every machine running it: sent - route-proxy on every machine running it: sent - build-agent on every machine running it: sent - mesh-build-go on every machine running it: sent - mesh-build-image on every machine running it: sent - mesh-build-node on every machine running it: sent - mesh-delivery-checker on every machine running it: sent - mesh-delivery-forge-bridge on every machine running it: sent - mesh-delivery-gate on every machine running it: sent - mesh-delivery-indexer on every machine running it: sent - mesh-delivery-view on every machine running it: sent - mesh-tools on every machine running it: sent - audit-logger on every machine running it: sent - baserow on every machine running it: sent - bazarr on every machine running it: sent - bookshelf on every machine running it: sent - confluence on every machine running it: sent - gitea on every machine running it: sent - gitlab on every machine running it: sent - grafana on every machine running it: sent - home-assistant on every machine running it: sent - icecast on every machine running it: sent - influxdb on every machine running it: sent - jackett on every machine running it: sent - jira on every machine running it: sent - kometa on every machine running it: sent - lab on every machine running it: sent - letta on every machine running it: sent - lidarr on every machine running it: sent - mailu on every machine running it: sent - mesh-catalog on every machine running it: sent - mesh-delivery-builder on every machine running it: sent - minio on every machine running it: sent - model-usage on every machine running it: sent - mongodb on every machine running it: sent - mosquitto on every machine running it: sent - mssql on every machine running it: sent - netcheck on every machine running it: sent - nextcloud on every machine running it: sent - nodered on every machine running it: sent - ombi on every machine running it: sent - openai-consumer on every machine running it: sent - radarr on every machine running it: sent - redis on every machine running it: sent - route-adapter on every machine running it: sent - searxng on every machine running it: sent - showcase on every machine running it: sent - sonarr on every machine running it: sent - tautulli on every machine running it: sent - umami on every machine running it: sent - unifi on every machine running it: sent - zsh on every machine running it: sent **Transitions** - 2026-10-22 21:52 (new) → proposed (announced): novox/mesh-controller#441's head announced - 2026-10-22 22:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-22 22:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-22 22:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-22 22:15 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-23 00:01 delivering → stopped (stop): its walk plan-1792707174627079192 was stopped by a person (mesh-controller): issue 1886 (the operator, 02:08: fix it right now): stuck for good on builder keys nothing running can reference; as an open plan it holds every merge check, including the fix mesh-controller #442. The fixed controller goes to novox by the bootstrap act (ADR 0522 §5); R4e's 8 + 40 remaining modules are carried on afterwards by a retry that resumes a hand-stopped plan (follow-up on issue 1886, note 7). The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 289bbf68e4 into main

2026-10-22 22:12:59 +00:00

mesh-tools deleted branch feat/r4e

2026-10-22 22:12:59 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#441