mesh-host

391 Commits 3 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
jochen	1fc1e74cc3	Judge whether what a module runs stays up, and say it (hq ADR 0240, to-be 48 Phase A) mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery delivered Details mesh/delivery-group group feat/a-module-says-how-it-is-healthy delivered: every member is delivered Details A container that crash-looped after its compose applied passed every check the gate had: nothing looked at what a module runs. The node-engine now judges every long-running resource on every look — one read of the runtime, one per service manager — keeps the restarts it counts across recreates and its own restarts, and says the state in every report and as an event on change, again every minute while not healthy. It reads only; nothing is restarted for being unhealthy.	2026-10-07 02:28:15 +02:00
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
jochen	31804bd8c2	Apply through one queue, and order what is applied and reported (hq to-be 45 Phase 2) A delivery and the five-minute reconcile were two paths that applied, ordered only by a lock, and each order it allowed was met live (issues 257, 261, 267). Now both only enqueue: one worker takes the newest declaration held when it starts, applies it once and makes one report, and reports leave in the order they are made. A declaration may carry the controller's lease epoch beside its sequence; one older than what this node applied is refused before anything is touched, counted, logged and reported. A report carries the declaration's epoch and sequence and the host's own report sequence, kept on disk so it goes on increasing across restarts and self-updates. Without an epoch, today's behaviour stands.	2026-10-06 11:54:10 +02:00

Author

SHA1

Message

Date

jochen

1fc1e74cc3

Judge whether what a module runs stays up, and say it (hq ADR 0240, to-be 48 Phase A)

mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

mesh/delivery-group group feat/a-module-says-how-it-is-healthy delivered: every member is delivered

Details

A container that crash-looped after its compose applied passed every check the
gate had: nothing looked at what a module runs. The node-engine now judges every
long-running resource on every look — one read of the runtime, one per service
manager — keeps the restarts it counts across recreates and its own restarts,
and says the state in every report and as an event on change, again every minute
while not healthy. It reads only; nothing is restarted for being unhealthy.

2026-10-07 02:28:15 +02:00

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

jochen

31804bd8c2

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

A delivery and the five-minute reconcile were two paths that applied, ordered only by a lock, and
each order it allowed was met live (issues 257, 261, 267). Now both only enqueue: one worker takes
the newest declaration held when it starts, applies it once and makes one report, and reports leave
in the order they are made.

A declaration may carry the controller's lease epoch beside its sequence; one older than what this
node applied is refused before anything is touched, counted, logged and reported. A report carries
the declaration's epoch and sequence and the host's own report sequence, kept on disk so it goes on
increasing across restarts and self-updates. Without an epoch, today's behaviour stands.

2026-10-06 11:54:10 +02:00