Registry milestone: mesh-networking (issue 1966) #3

2026-11-04T17:50:47Z

mesh-tools commented

2026-11-04 17:50:47 +00:00

The registry milestone (issue 1966; ADR 0605-0636 as hq's designs name them), taken in onto its trunks after milestone 47/B0 as milestone 47/G's first step (design 47; issue 1921 notes 54-61).

One delivery group, branch feat/registry-milestone in mesh-sdk, mesh-contracts, mesh-delivery, mesh-host, mesh-tools, mesh-catalog and mesh-networking: one check, one Approve. No member names another's version (ADR 0573); every mesh package is required at the zero version.

This member: no change in this step.

The registry's reviewed heads (three rounds, 2026-11-04 to 11-06) were never pushed until now; the check of 068b7d23cf1a judged the heads of 2026-11-04. The trunk step was prepared and reviewed in three rounds (2026-11-07): the merge resolutions keep B0's facts and checking-program rules and the registry's generated types; every check composes with the composer at the node-engine member's head, else its trunk; a module the running indexer refuses but the check's own validator accepts is composed and named in the verdict with its build awaited, never passed silently; the checking program answers only new or changed seat definitions when given the reader's digests, and without them (the running B0 checker) only each seat's own description, 171 KB under the 256 KiB bound.

Rules bent, said here: mesh-delivery stays over its test budget (662 unit, 68 integration; was 675 and 68) and mesh-host over unit (1745; was 1746), falling. Out of this step, noted on issue 1921: three asks carry the whole seat list (~430 KB) bounded only by the bus's 1 MiB; the trunk case of the manifest validator is given the heads' seats.

Reviewed-by: mesh-code-reviewer@shanks at 9ee0ffe3c0

https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

The registry milestone (issue 1966; ADR 0605-0636 as hq's designs name them), taken in onto its trunks after milestone 47/B0 as milestone 47/G's first step (design 47; issue 1921 notes 54-61). One delivery group, branch feat/registry-milestone in mesh-sdk, mesh-contracts, mesh-delivery, mesh-host, mesh-tools, mesh-catalog and mesh-networking: one check, one Approve. No member names another's version (ADR 0573); every mesh package is required at the zero version. This member: no change in this step. The registry's reviewed heads (three rounds, 2026-11-04 to 11-06) were never pushed until now; the check of 068b7d23cf1a judged the heads of 2026-11-04. The trunk step was prepared and reviewed in three rounds (2026-11-07): the merge resolutions keep B0's facts and checking-program rules and the registry's generated types; every check composes with the composer at the node-engine member's head, else its trunk; a module the running indexer refuses but the check's own validator accepts is composed and named in the verdict with its build awaited, never passed silently; the checking program answers only new or changed seat definitions when given the reader's digests, and without them (the running B0 checker) only each seat's own description, 171 KB under the 256 KiB bound. Rules bent, said here: mesh-delivery stays over its test budget (662 unit, 68 integration; was 675 and 68) and mesh-host over unit (1745; was 1746), falling. Out of this step, noted on issue 1921: three asks carry the whole seat list (~430 KB) bounded only by the bus's 1 MiB; the trunk case of the manifest validator is given the heads' seats. Reviewed-by: mesh-code-reviewer@shanks at 9ee0ffe3c0b6b64b0e862626b9785afb810d4fa9 https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools added 3 commits 2026-11-04 17:50:47 +00:00

Pin mesh-sdk c54648e74346 and mesh-contracts ec9529022c44, the group's heads (issue 1966) 39196381de

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Pin mesh-sdk e5d89c5eedb5 and mesh-contracts 347a3053580a, the group's heads after review round 2 (issue 1966) 3c8553a6c3

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Pin mesh-sdk 05b3e2e1b94f and mesh-contracts ae5266e77639, the group's final heads (issue 1966)

mesh/delivery-group group feat/registry-milestone checking: 7 of 7 member(s) ready

Details

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check checking 0c0a12f1c929 on efdcc9daef2d | novox/mesh-networking#3 in group feat/registry-milestone

0c0a12f1c9

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

mesh-tools commented

2026-11-04 17:51:09 +00:00

Delivery novox/mesh-networking@9ee0ffe3c0b6 — merged since 2026-11-07T14:19:58Z

Source — source.main moved to novox/mesh-networking@5af7189cad. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group feat/registry-milestone: novox/mesh-catalog@67d9ccb1d4, novox/mesh-contracts@b77560786a, novox/mesh-delivery@4735fc0b5f, novox/mesh-host@cb7a444a56, novox/mesh-networking@9ee0ffe3c0, novox/mesh-sdk@d932546703, novox/mesh-tools@6c05e42626

composed together: fail — the checker's verdict at the members' heads (f7ed14f6b430): integration: meshbuildgo/cmd/mesh-build-go.TestAComposeAskIsBuiltOnceAndAnsweredOnTheBus

Transitions

2026-11-07 02:55 (new) → proposed (announced): novox/mesh-networking#3's head announced
2026-11-07 02:55 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-07 14:19 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-networking@9ee0ffe3c0b6` — **merged** since 2026-11-07T14:19:58Z **Source** — source.main moved to novox/mesh-networking@5af7189cad82. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/registry-milestone`: novox/mesh-catalog@67d9ccb1d455, novox/mesh-contracts@b77560786a6a, novox/mesh-delivery@4735fc0b5fdb, novox/mesh-host@cb7a444a5634, novox/mesh-networking@9ee0ffe3c0b6, novox/mesh-sdk@d93254670307, novox/mesh-tools@6c05e4262641 - composed together: fail — the checker's verdict at the members' heads (f7ed14f6b430): integration: meshbuildgo/cmd/mesh-build-go.TestAComposeAskIsBuiltOnceAndAnsweredOnTheBus **Transitions** - 2026-11-07 02:55 (new) → proposed (announced): novox/mesh-networking#3's head announced - 2026-11-07 02:55 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-07 14:19 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools commented

2026-11-05 23:47:37 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools commented

2026-11-07 00:32:43 +00:00

mesh-delivery: not merged. The merge of this pull request into main at 0c0a12f1c9 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

mesh-delivery: **not merged.** The merge of this pull request into main at 0c0a12f1c929b3995bad58aa149e1161f74dad4a was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

nox-agent added 14 commits 2026-11-07 02:54:18 +00:00

mesh-connectivity-contracts: the Connectivity domain's contracts module moves here from mesh-contracts; the-private-network defined whole, no client (ADR 0636 §6; issue 1966) dd7dfdd6f7

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

mesh-wireguard: the module that holds the-private-network, with its manifest and peer generator its own package (ADR 0636 §6; issue 1966) be74c94151

The names and the manifest come from mesh-sdk's overlay, the peer graph, the generator and the declaration from the node-engine's internal/overlay; the value's layout is the seat's contract in mesh-connectivity-contracts.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

route-proxy: provisions and the provider come from the provisioner's client, not mesh-sdk (N-1, ADR 0634 §4; issue 1966) acaebc5ddf

The requires of the two mesh-contracts modules carry a placeholder version the group's re-pin replaces.

mesh-connectivity-contracts: each seat's definition names its domain, Connectivity (the indexer's domain rule; ADR 0634 §9; issue 1966) f5fc1e4ebc

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-wireguard: the modules the mesh provides itself are its overlay package's, and the seat's name is the generated package's (ADR 0636 §6; issue 1966) 5885ab600a

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

route-proxy: placement is read through the module assigner's client, and a bus address is said without its credential by the proxy's own helper (N-1, ADR 0634 §4; issue 1966) e313ac9d3b

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-wireguard: the two provisions say their credential form (none), as the manifest validator requires of every offer (V1; issue 1966) 122f640963

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

Require every mesh package of the group at the floor version (ADR 0573 sections 2 and 4, issue 1966) 2020b87df0

A member's go.mod names the oldest version a module accepts; the check builds the group's own heads whatever it names. go.sum lines of mesh packages are left out.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

No client names a holder: each reader keeps its own constant, held to its manifest (ADR 0625 section 4, issue 1966) e1eb98fcbc

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

No client names the holder of the seat mesh-provisioner: each reader keeps its own constant, held to its manifest (ADR 0625 section 4, issue 1966) db50239373

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

Route-proxy and the overlay name the assigner's new places: the contracts' go/ path and the state assignments (issue 1966) 2f0b7c9741

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

Complete go.mod and go.sum for the externals each module builds with 34f5757d94

A check's tests run without network, so each module must carry every external module it builds with.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

Take tidy's go.mod whole: mesh requirements at the zero version only, unused ones dropped 4d1f9acae1

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

gofmt the file the group try listed

mesh/delivery merged: source.main moved to novox/mesh-networking@5af7189cad82

Details

mesh/delivery-group group feat/registry-milestone merged: every member is merged

Details

mesh/check checking 9ee0ffe3c0b6 on 5af7189cad82 | novox/mesh-networking#3 in group feat/registry-milestone

9ee0ffe3c0

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools commented

2026-11-07 03:51:16 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools commented

2026-11-07 06:34:34 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools commented

2026-11-07 10:30:37 +00:00

mesh-delivery: not merged. The merge of this pull request into main at 9ee0ffe3c0 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

mesh-delivery: **not merged.** The merge of this pull request into main at 9ee0ffe3c0b6b64b0e862626b9785afb810d4fa9 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

mesh-tools merged commit 5af7189cad into main

2026-11-07 14:19:55 +00:00

mesh-tools deleted branch feat/registry-milestone

2026-11-07 14:19:55 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-networking#3