mesh-host

Files

T

jochen 6e1bcdbde4 Say again what was last applied when the mesh asks (hq to-be 45 Phase 3, the report verb)

The controller's healer H1 answers a send that went unreported by asking the
machine first: a report lost on its way (issue 264) needs no second send. The
node-engine now hears mesh.node.<self>.ask.report on core NATS and enqueues a
reconcile whose account is said whether or not it is news; a delivery waiting
meanwhile is applied and reported instead. The answer is an ordinary report on
its own subject, so the node publishes nothing new and answers nobody's inbox.

The genesis lock grants the controller the healer-acted seat event, which it
now composes; the genesis test in mesh-controller holds the two equal.

2026-10-06 14:05:02 +02:00

apply

Hand a whole file to its new owner instead of removing it first (hq ADR 0223)

2026-10-05 23:35:40 +02:00

bootstrap

An apply leaves a container a maintenance window holds still (hq issue 224)

2026-10-05 18:27:04 +02:00

bundle

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

declaration

Apply through one queue, and order what is applied and reported (hq to-be 45 Phase 2)