R4g+R5 (mesh-delivery): builder and checker put asks, the assigner and its composition check, the view's wants and backlog (design 47) #27

Merged

jschoubben merged 58 commits from feat/r4g into main 2026-10-23 17:49:02 +00:00

Conversation 1 Commits 58 Files Changed 127

+6773 -2817

mesh-tools commented 2026-10-23 15:00:50 +00:00

Member

Copy Link

Copy Source

Design 47's last milestone, R4g+R5, one delivery group on feat/r4g.

• Builder and checker put asks on the build seats' streams; the hold, node choice and capacity deleted; the check's own repository placed beside it; mesh-lab judged; a check keeps what an earlier check of the same heads passed (issue 1887, issue 1685, issue 1917; ADR 0525, 0529).
• New module mesh-delivery-assigner: wants by six rules, differences, the composition check the checker reads, hold asks (issue 1297; ADR 0528, 0537).
• The view's wants page, backlog of asks, answers in the view; the teller reads them; the watchman pulses running steps (issues 1908, 1909).
• Fixes folded in: issue 1910, issue 1912; indexer issue 1900 travels with this delivery.
• merge-check.sh gone (issue 1295).
• The node-engine's tests have the controller beside them: with mesh-host's merge-check.sh gone the checker judges mesh-host, whose genesis tests read the controller's manifest (issue 1295).

Reviewed-by: review-r4g-2@shanks at b2c545c40a
Pushed-by: lead-47@shanks

Design 47's last milestone, R4g+R5, one delivery group on feat/r4g. - Builder and checker put asks on the build seats' streams; the hold, node choice and capacity deleted; the check's own repository placed beside it; mesh-lab judged; a check keeps what an earlier check of the same heads passed (issue 1887, issue 1685, issue 1917; ADR 0525, 0529). - New module mesh-delivery-assigner: wants by six rules, differences, the composition check the checker reads, hold asks (issue 1297; ADR 0528, 0537). - The view's wants page, backlog of asks, answers in the view; the teller reads them; the watchman pulses running steps (issues 1908, 1909). - Fixes folded in: issue 1910, issue 1912; indexer issue 1900 travels with this delivery. - merge-check.sh gone (issue 1295). - The node-engine's tests have the controller beside them: with mesh-host's merge-check.sh gone the checker judges mesh-host, whose genesis tests read the controller's manifest (issue 1295). Reviewed-by: review-r4g-2@shanks at b2c545c40aecac8199d4df884ad1257d6698d153 Pushed-by: lead-47@shanks

mesh-tools added 55 commits 2026-10-23 15:00:50 +00:00

Show every difference between the assigner's wants and the controller's sends with its rule, so the operator sees what holds a node back (issue 1297 B8) 57b0030258

Let the view answer the assigner's asks that need no proof, under the ask's view key, and refuse the merge's Approve on the phone's behalf (issue 1297 B9a) f7dd4ab586

Give the command an answer verb, so the operator answers a hold or restore ask from a terminal as in the page (issue 1297 B9b) e7ed48b81a

Make the module mesh-delivery-assigner: its manifest's reads and states, its own credential and the states it announces, so the controller grants it what R5 reads (issue 1297, subtask B2a; ADR 0528, ADR 0429 §1) 034a6de9a7

Fill an assigner ask's answer from the view's answer under its view key, once and never for an ask that needs proof (issue 1297 B10) a48279b31a

Start the assigner whole on an embedded bus in an integration test: it says its three states and refuses to start without a bucket it reads (issue 1297, subtask B2b) c2b7b8867e

Take the assigner's ask in the SDK's layout and name the asking in the view's answer, so a stale answer never fills a later asking (issue 1297 B9 and B10) 57258b6fa4

Compose the machines a change touches, from the trunk's and the change's manifests and the controller's assignments on the bus, and write the verdict under the checker's key; what needs the facts snapshot is said as not judged (issue 1297, subtasks B3a-B3c; ADR 0446 clauses 1-3, ADR 0528 clause 5, ADR 0482 clause 3 as R4g delivers it) d8599855e1

Read the assigner's composition into the checker's verdict in place of 'not yet run', failing a check whose composition failed, naming its machine (issue 1297, subtask B3d; ADR 0528 clause 5) 5091cab652

Write each node's want by the six rules, the canary the first online node by name, and hold a fingerprint whose health failed with its nodes set back, so R5's wants can be compared with what the controller sends (issue 1297, subtasks B4a-B4b; ADR 0429 §6, ADR 0528 clauses 1 and 3, ADR 0435 §3) 016385751d

Compare each node's want with the fingerprint of the build the controller sends it, explaining a difference by the rule that holds the want back or saying it unexplained (issue 1297, subtask B5a; ADR 0528 clause 4) d7ba5aa91e

Write every difference between a want and what the controller sends, and delete one that ended, so the view and acceptance test 17 read them on the bus (issue 1297, subtask B5b; ADR 0528 clause 4) ed98a7519e

Place the change's own repository beside it at its trunk, so a shrink-only list test compares with the trunk's copy at $MESH_CHECK_BESIDE/<name> (issue 1887 A12, ADR 0529 §2) 0f7091e4ac

Pin the assigner and the checker to the SDK commit that holds the assigner's ask value, so both build on the layouts the view reads (issue 1297, subtask B1c) c9ee92a4ab

Judge a repository the mesh knows no module of with both build modules, so mesh-lab's nested Go modules and its npm test both run (issue 1887 A12) 4c98841d2a

Wait for the assigner's composition only while the assigner is online, say at once that it is not judged when it is not, and take it in when the assigner writes it later, so no check waits its bound for a composition nobody makes (issue 1297, B3d) 7cbb1c4207

Take the words of a module the change removes from mesh-sdk in the indexer and the assigner, so the assigner's reading of a removal cannot drift from what the indexer writes (issue 1297, B3b) d5868c178f

Build each build module's part of a fingerprint as one ask on its seat's stream, named in the key before it is put, so the builder chooses no node, holds no capacity and never asks twice (issue 1887 A4a, A4b, A4c, ADR 0525 §1-§6) 9f27e2b1f8

Merge branch 'feat/r4g-assigner' into feat/r4g 173178df86

Merge branch 'feat/r4g-view' into feat/r4g 2227e7a81f

Pin mesh-sdk at feat/r4g's head c3915ffb, the merge of lane B's layouts, so every r4g module builds against one SDK ... 271d1ca759

go.sum gains its lines from go mod tidy once mesh-sdk feat/r4g is pushed.

Judge each pull request's check as one ask on the build seats' check stream, a re-judge on recheck, so the checker chooses no node and a lost node's check is redelivered, not moved (issue 1887 A5a, ADR 0525 §1, §3, ADR 0536 §4) e4b639c6de

Delete the checker's hold, its own capacity and places, its node moves and its read of the controller's plans-building, so a check waits only in the build seats' streams (issue 1887 A5b, closes 1685; ADR 0525 §4, §7) d9d1e57e3a

Delete merge-check.sh; the checker's levels and the build module's fetch beside run what it ran (issue 1295, S8; ADR 0529) f37e5d5fa1

Keep the asks state and write the ask about a held fingerprint, so the view's and the teller's read of mesh-delivery-assigner.asks is granted and has something to answer (issue 1297, review round 1 item 1; ADR 0528 clause 6) 77af82cfa2

Merge feat/r4g-asks into the view lane, keeping the checker's assigner compositions 179664898a

Start the checker whole with the assigner's verdict on the bus and read its line, the level 1297/AC3 asks (issue 1297, review round 1 item 2) d4977d9c9d

Judge hq as any repository, so its pull requests get a verdict and mesh/check from its Go tests and no script judges it (issue 1887 A10, ADR 0527 §2) 69577f739d

Look the assigner's compositions bucket up at each check until it is there, so an assigner delivered after the checker started is read without a restart (issue 1297, review round 1 item 3) d0354574c6

Mirror a waiting build ask as a pulse until a node writes its step, and drop the read of the controller's checks-running (issue 1887 A8b) a8ba5c2fd5

Show the backlog of build asks per language and kind: waiting, held by a node, and the oldest waiting ask's age (issue 1887 A8a) 79ef768ea4

Format the watchman's integration test (issue 1887 A8b) 50836eb4d6

Compute every module's fingerprint with no builder input and read no build-agent record for it, so a change of the builder rebuilds nothing (issue 1887 I1, ADR 0530 §1) a4629bc649

Merge branch 'feat/r4g-assigner' into feat/r4g 0463f21026

Merge branch 'feat/r4g-asks' into feat/r4g ... 527f87f94c

# Conflicts:
#	modules/mesh-delivery-checker/cmd/mesh-delivery-checker/judge.go
#	modules/mesh-delivery-checker/manifest_test.go
#	modules/mesh-delivery-checker/module.json

Merge branch 'feat/r4g-view' into feat/r4g 66be3dd0e4

Merge branch 'feat/r4g-scripts' into feat/r4g dd8e05142d

Pin mesh-sdk at feat/r4g's head 9205222a, the merge of lanes A, B, S8 and F1, so every module r4g touches builds against one SDK ... e4a40a1cb0

go.sum gains its lines from go mod tidy once mesh-sdk feat/r4g is pushed.

Record the checksums of mesh-sdk feat/r4g 9205222a for the group's modules (R4g) 95f52afab2

Record the assigner's full requirements and mesh-sdk feat/r4g's checksums, so the new module builds without a workspace (R4g) 1b019f0353

Name in every composition, by machine, those that could run a moved or added module and are not assigned it and those whose grants alone the change alters, as not judged, as ADR 0537 clause 1 asks (issue 1297) 97b42e3f0d

Pulse a build ask only from when a node takes it, and end the pulse with its step, so a waiting ask is a backlog and not a stuck row (issue 1908) e927469460

Test that an ask running when the watchman starts gets its pulse from the steps that stand (issue 1909) 76bc810bda

Drop the view's use of the build seats: it reads their workers and publishes no ask (issue 1887 A8a) c0f24f56b5

Put again, under its own id, an ask a build key names that neither its stream holds nor any node ran, so a builder that stopped between naming and putting it leaves no key waiting for an ask nobody put (issue 1910) 84b2c92ccf

Stop watching the node-engine's have in the checker: a check's asks wait in the build seats' streams, which redeliver a lost node's ask, so no check fails for want of a node; presence stays for an unheard forge and the assigner's presence (issue 1912) 37860d46a0

Bound a build or check ask's step from its start, and drop the checker's whole-check bound, so asks waiting in the streams during a large rebuild are never failed and asked twice (issue 1887, review round 2 item 1; ADR 0525 §3, §6) 5ddc221833

Merge remote-tracking branch 'origin/feat/r4g' into feat/r4g ... 357e28f31d

# Conflicts:
#	modules/mesh-delivery-builder/internal/build/run_test.go

Count the asks the builder puts and read their kind in its integration test, so 1887/AC1 is proven on the real bus (issue 1887, review round 2 item 3) bac82bb91e

Prove on the real bus that a builder started again while its asks waited puts no second ask (issue 1887 AC3, review round 2 item 2) ce51457974

Say in the checker's status that a check without a verdict waits in a build seat's stream, not behind a plan key or a capacity, as A5b left it (issue 1887, review round 2 item 4) 52d8b9b753

Say what the builder, the indexer and the watchman do since R4g in their comments: no build-agent is asked, no build record moves a fingerprint, no checks-running bucket is mirrored (issue 1887, review round 2 item 6) d32ec6b7f8

Say the unit level's gofmt and go vet time in the check's line, and pin the group's mesh-sdk head that carries it (issue 1887 D7-go, review round 2 item 5) d3561923aa

Bound a running build step's pulse by the step's own bound from its start, since nothing rewrites the key while it runs (issue 1908) c7bddbbeab

Read an ask's stream at take-over by its name, as the broker grants it, and wait for the ask when that read fails rather than fail a key whose build may still finish (issue 1910) b83af04f0c

mesh-tools commented 2026-10-23 15:01:02 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-delivery@b2c545c40aec — failed since 2026-10-23T17:59:26Z

Covered: covered after its failure: a later walk that contains it was delivered: plan-1792777718506798022 (novox/mesh-delivery at fae4d48e into main, done, contains its merge fae4d48e)

Delivery plan — builds mesh-delivery-builder, mesh-delivery-checker, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view, mesh-delivery-watchman, new: modules/mesh-delivery-assigner → novox, shanks; no bus step

• tier 0: mesh-delivery-builder, mesh-delivery-checker, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view, mesh-delivery-watchman
• novox: receives mesh-delivery-checker, mesh-delivery-indexer, mesh-delivery-teller, 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-view is judged on its first machine

Group feat/r4g: novox/hq@e8bd9171cd, novox/mesh-catalog@454fb8a918, novox/mesh-controller@c9a7102bc5, novox/mesh-delivery@b2c545c40a, novox/mesh-host@4b4bb09a05, novox/mesh-lab@4653b17e18, novox/mesh-media-catalog@f4f0bbcfe5, novox/mesh-sdk@a2c813a6b4, novox/mesh-tools-go@5023de36fd, novox/mesh-tools@860043fd7f, novox/okioki@e67d21e8b4

Machines

• claude-code on every machine running it: sent
• mesh-controller on every machine running it: sent
• mesh-delivery-indexer on every machine running it: sent
• mesh-sdk on every machine running it: sent
• node-tools 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-builder on every machine running it: sent
• mesh-delivery-checker on every machine running it: sent
• mesh-delivery-gate on every machine running it: sent
• mesh-delivery-teller on every machine running it: sent
• mesh-delivery-view on every machine running it: sent
• mesh-delivery-watchman on every machine running it: sent
• mesh-issues on every machine running it: sent
• audit-logger 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
• jira on every machine running it: sent
• lidarr on every machine running it: sent
• mesh-catalog on every machine running it: sent
• model-usage on every machine running it: sent
• mosquitto 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
• 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

Transitions

• 2026-10-23 16:38 (new) → proposed (announced): novox/mesh-delivery#27's head announced
• 2026-10-23 16:46 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-23 16:46 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
• 2026-10-23 17:49 rejected → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
• 2026-10-23 17:55 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
• 2026-10-23 17:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-delivery@b2c545c40aec` — **failed** since 2026-10-23T17:59:26Z **Covered**: covered after its failure: a later walk that contains it was delivered: plan-1792777718506798022 (novox/mesh-delivery at fae4d48e into main, done, contains its merge fae4d48e) **Delivery plan** — builds mesh-delivery-builder, mesh-delivery-checker, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view, mesh-delivery-watchman, new: modules/mesh-delivery-assigner → novox, shanks; no bus step - tier 0: mesh-delivery-builder, mesh-delivery-checker, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view, mesh-delivery-watchman - novox: receives mesh-delivery-checker, mesh-delivery-indexer, mesh-delivery-teller, 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-view is judged on its first machine **Group** `feat/r4g`: novox/hq@e8bd9171cdbc, novox/mesh-catalog@454fb8a918ad, novox/mesh-controller@c9a7102bc53b, novox/mesh-delivery@b2c545c40aec, novox/mesh-host@4b4bb09a05a0, novox/mesh-lab@4653b17e18a7, novox/mesh-media-catalog@f4f0bbcfe59c, novox/mesh-sdk@a2c813a6b468, novox/mesh-tools-go@5023de36fded, novox/mesh-tools@860043fd7fa0, novox/okioki@e67d21e8b448 **Machines** - claude-code on every machine running it: sent - mesh-controller on every machine running it: sent - mesh-delivery-indexer on every machine running it: sent - mesh-sdk on every machine running it: sent - node-tools 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-builder on every machine running it: sent - mesh-delivery-checker on every machine running it: sent - mesh-delivery-gate on every machine running it: sent - mesh-delivery-teller on every machine running it: sent - mesh-delivery-view on every machine running it: sent - mesh-delivery-watchman on every machine running it: sent - mesh-issues on every machine running it: sent - audit-logger 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 - jira on every machine running it: sent - lidarr on every machine running it: sent - mesh-catalog on every machine running it: sent - model-usage on every machine running it: sent - mosquitto 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 - 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 **Transitions** - 2026-10-23 16:38 (new) → proposed (announced): novox/mesh-delivery#27's head announced - 2026-10-23 16:46 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-23 16:46 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-23 17:49 rejected → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-23 17:55 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go` - 2026-10-23 17:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben added 1 commit 2026-10-23 15:06:11 +00:00

Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied fad96ae67b

jschoubben added 1 commit 2026-10-23 15:18:39 +00:00

Prove that a second check of the same heads keeps every package the first passed, the digest being taken inside the check ask as the build module answers it (issue 1917) ad26670996

jschoubben added 1 commit 2026-10-23 16:37:58 +00:00

Place mesh-controller beside the node-engine's tests, which read its manifest (issue 1295, R4g) b2c545c40a

jschoubben merged commit fae4d48e09 into main 2026-10-23 17:49:02 +00:00

jschoubben deleted branch feat/r4g 2026-10-23 17:49:02 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

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

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#27