The mesh says what it applied, and the replay has an address it may use #129

2026-09-28T14:07:19Z

mesh-admin commented

2026-09-28 14:07:19 +00:00

No description provided.

mesh-admin added 1 commit 2026-09-28 14:07:19 +00:00

The mesh says what it applied, and the replay has an address it may use 1ebad3786c

The pipeline was observable from a merge to an artifact and went dark where it touched a machine: a
node's report is control traffic only the control plane reads, so nothing said which version a
machine runs, or that it refused to (novox/hq ADR 0134). The control plane now states both under the
seat it holds — a role's events belong to the role and keep their address when the holder is
replaced — and only when the report is news, because a machine reconciles every minute and a fact per
report would be a fact per minute per machine.

Whether a report is news is the store's answer: it holds the previous one, so the listener returns it
and the server states the fact. That also gives the catch-up replay a subject the controller may
publish: it was published as a module's event from a module called "control-plane", which does not
exist, so the controller's own account refused it and every catalogue that asked what it missed was
answered with nothing.

mesh-admin merged commit 89e152dfe2 into main

2026-09-28 14:07:20 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#129