mesh-controller

1,462 Commits 17 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ad3b4f185b	Judge a leaf module on one healthy reading, a core module on three (hq issue 524) mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without … Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery superseded: a newer head of the same pull request Details ADR 0282 decided readings by class and ADR 0304 took a leaf module to one, but the gate never learned it: every build, leaf or core, needed three readings over at least two minutes, so a container module that was healthy at once still waited about two and a half minutes on its first machine. The number of readings and the settle time now follow the module's class: three after two minutes for the controller's own path and the resolver, one for every other module. Tests that judge a gate's other rules keep leaf modules on three readings.	2026-10-12 01:08:14 +02:00
jochen	a5e8baf6da	Register a module only from the repository the catalogue builds it from An agent could make a repository of its own, or fork one the mesh builds from, commit a module.json naming sudo or mesh-host, and ask the build verb for it: the outcome was registered under that name, and the next push made whoever wrote it root on every node (novox/hq ADR 0266 §7, the review of 2026-10-09). The trunk rule checked the trunk of the repository built, which was the agent's. The take-in, which every outcome reaches whichever verb asked it, now registers a module only from its registered repository, and a new module only from a repository the catalogue already builds from (a merge adding one); anything else only when the build request was kept as asked at the controller's terminal (migration 0084). Through a verb, a build of a repository the catalogue builds nothing from is not asked at all.	2026-10-09 12:37:18 +02:00
jschoubben	792352dfad	Read a rebuild of an unchanged source as no move, whatever image digest it made (hq issue 280) mesh/merge-gate error: the check could not run: a throwaway postgres:17-alpine could not be raised: docker run --label mesh.build=build-1791317509716888018… mesh/delivery delivered Details An image is not byte-reproducible, so ADR 0236's 'same artifacts is no move' never held for one: a catalogue merge that did not touch the bus rebuilt it, and every send to the control node waited for a planned bus upgrade. The builder now records a source fingerprint per build (module tree, context trees, bases and toolchains by digest). A rebuild with the fingerprint of the build it repeats is registered with that build's artifacts, handed to modules standing on it, holds no push, demands no bus step, and a plan sends and gates nothing for it. Identical artifacts remain a second way to be no move.	2026-10-06 22:09:11 +02:00

Author

SHA1

Message

Date

jschoubben

ad3b4f185b

Judge a leaf module on one healthy reading, a core module on three (hq issue 524)

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

Details

mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…

Details

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

Details

ADR 0282 decided readings by class and ADR 0304 took a leaf module to
one, but the gate never learned it: every build, leaf or core, needed
three readings over at least two minutes, so a container module that
was healthy at once still waited about two and a half minutes on its
first machine. The number of readings and the settle time now follow
the module's class: three after two minutes for the controller's own
path and the resolver, one for every other module. Tests that judge a
gate's other rules keep leaf modules on three readings.

2026-10-12 01:08:14 +02:00

jochen

a5e8baf6da

Register a module only from the repository the catalogue builds it from

An agent could make a repository of its own, or fork one the mesh builds
from, commit a module.json naming sudo or mesh-host, and ask the build verb
for it: the outcome was registered under that name, and the next push made
whoever wrote it root on every node (novox/hq ADR 0266 §7, the review of
2026-10-09). The trunk rule checked the trunk of the repository built, which
was the agent's.

The take-in, which every outcome reaches whichever verb asked it, now
registers a module only from its registered repository, and a new module only
from a repository the catalogue already builds from (a merge adding one);
anything else only when the build request was kept as asked at the
controller's terminal (migration 0084). Through a verb, a build of a
repository the catalogue builds nothing from is not asked at all.

2026-10-09 12:37:18 +02:00

jschoubben

792352dfad

Read a rebuild of an unchanged source as no move, whatever image digest it made (hq issue 280)

mesh/merge-gate error: the check could not run: a throwaway postgres:17-alpine could not be raised: docker run --label mesh.build=build-1791317509716888018…

mesh/delivery delivered

Details

An image is not byte-reproducible, so ADR 0236's 'same artifacts is no move'
never held for one: a catalogue merge that did not touch the bus rebuilt it,
and every send to the control node waited for a planned bus upgrade.

The builder now records a source fingerprint per build (module tree, context
trees, bases and toolchains by digest). A rebuild with the fingerprint of the
build it repeats is registered with that build's artifacts, handed to modules
standing on it, holds no push, demands no bus step, and a plan sends and
gates nothing for it. Identical artifacts remain a second way to be no move.

2026-10-06 22:09:11 +02:00