ADR 0141: the host delivers its own successor, and versions live side by side

novox/hq

The supervision was already right — a clean exit means the host stood aside and
the launcher runs what is on disk, failures are counted, and a rollback happens
at the limit. Two things made it dead code: nothing told the running host a
successor was waiting, and the rollback resolved its known-good version through
pacman, which no machine here uses and which two of three operating systems do
not have.

Keeping a version rather than a path was the clue. Versions live side by side in
directories named for them; the newest runs; the running one stands aside between
reconciles; a reconcile that completes records itself and retires what is older
than its predecessor; rollback starts that predecessor. No new resource kind and
nothing new on the bus — an archive already fetches by digest, and the path
written is never the path executing.

Answers issue 142.

This commit is contained in:

jschoubben

2026-09-29 00:22:04 +02:00

parent 61dc90e508

commit a815433214

4 changed files with 174 additions and 2 deletions

									
										04-ISSUES/142-the-host-is-the-one-thing-the-mesh-does-not-deliver/00-report.md
									
		+1
		-1
	
												View File
												
				@@ -6,7 +6,7 @@ located-in:

				  - mesh-host cmd/mesh-host

				  - mesh-controller (no build source for the host; no resource delivers it)

				fixed-by:

				amended-design:

				amended-design: 03-DESIGN/01-to-be/05-the-node-host.md

				---

				# 142 — The host is the one thing the mesh does not deliver