ADR 0133 and 0134: who runs migrations, and the mesh saying what it applied #160

2026-09-28T09:45:48Z

mesh-admin commented

2026-09-28 09:45:48 +00:00

No description provided.

mesh-admin added 1 commit 2026-09-28 09:45:49 +00:00

ADR 0133 and 0134: who runs migrations, and the mesh saying what it applied 891c7a945e

0133 — a module owns its migrations and the mesh owns when they run. A container declares what must
run before it; the mesh derives the gated step from the resource it precedes, so the image, the
environment and the credentials come from the one place they are described. The module owns the SQL,
the dialect and the lock; the mesh owns the moment and refuses to start a version whose step failed.
Per node, with no level: a step that ran once somewhere leaves every other machine ungated, and
'once, mesh-wide' is what holding a seat already means.

0134 — the pipeline is observable from a merge to an artifact and goes dark at the machine. What a
node now runs, and what it refused, become facts under the control plane's own seat, emitted when
what a machine runs changes rather than on every convergence pass.

Design 32's lifecycle carries both; issue 133 points at them as what ends the matter it opened.

mesh-admin merged commit 74ba3ff1d4 into main

2026-09-28 09:45:49 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#160