mesh-controller

Archived

This repository has been archived on 2026-11-02. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Files

T

History

jochen 82fe44b380

mesh/delivery-group group feat/node-uplink-verbs ready: every member ready, and composed together they pass

Details

mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…

Details

mesh/repo-check fail: its merge-check.sh failed: FAIL github.com/novox/mesh-controller/cmd/mesh-controller 1800.041s

Details

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

Details

Give the uplink seat its verbs, staged until its holders serve them (hq ADR 0241)

What a machine resolves through and over which links had no tool: the
resolver file and its writer, and each link with its routes and resolvers,
are now verbs of node-uplink, the same whatever manages the network. A verb
required at once would refuse every holder before the catalogue could serve
it, and a stored one would be required by an older controller, so it is
staged: promised and routed, never stored, and not yet a condition of
holding.

2026-10-07 19:16:19 +02:00

artifacts

Keep a facts snapshot for merge checks, and say when it goes stale (hq to-be 45 Phase 5, S14)

2026-10-06 20:31:10 +02:00

broker

Read how a module says each resource is ready, and send it to engines that read it (hq ADR 0240, to-be 48 Phase B)

2026-10-07 16:17:50 +02:00

builder

Remove what an earlier delivery of a check left before raising its store again

2026-10-07 02:17:46 +02:00

catalogue

Give the uplink seat its verbs, staged until its holders serve them (hq ADR 0241)