mesh-host

Files

T

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

declared_test.go

A node that loses its mesh comes back on its own

2026-08-29 20:17:49 +02:00

declared.go

Refuse a declaration for the other mode, or older than the mesh's last, and say what an apply would change first

2026-09-23 23:15:28 +02:00

former_test.go

A take is a comparison: the host's facts, former targets, and strays (hq ADR 0163)

2026-10-01 21:24:37 +02:00

lock_test.go

Refuse every file once the mesh has spoken, plan the cutover as one, and let the kept declaration repair the mode