to-be 27: the three gaps answered #132

2026-09-26T15:44:46Z

jschoubben commented

2026-09-26 15:44:46 +00:00

Operator's answers, 2026-09-26: the root is a node setting defaulting under /var/lib; the subtree question dissolves (the mesh's own writes need no module-visible reservation — a module requires a host-path and receives a location, the mesh's plumbing is placed where the mesh chooses); resolution happens in the controller at declaration composition, so the wire format and the host's apply are unchanged (modulo issue 126's spec-comparison fix). Retirement stays per-module data migration with verification — the novox six-module window is the worked example.

Operator's answers, 2026-09-26: the root is a node setting defaulting under `/var/lib`; the subtree question dissolves (the mesh's own writes need no module-visible reservation — a module requires a `host-path` and receives a location, the mesh's plumbing is placed where the mesh chooses); resolution happens in the controller at declaration composition, so the wire format and the host's apply are unchanged (modulo issue 126's spec-comparison fix). Retirement stays per-module data migration with verification — the novox six-module window is the worked example.

jschoubben added 1 commit 2026-09-26 15:44:46 +00:00

to-be 27: the three gaps answered — root is a node setting, the mesh's writes need no module-visible reservation, resolution is the controller's at composition db142ffa26

jschoubben merged commit dc80116b09 into main

2026-09-26 15:44:54 +00:00

jschoubben deleted branch design/to-be-27-gaps-answered

2026-09-26 15:44:54 +00:00

jschoubben referenced this pull request

2026-09-26 16:56:49 +00:00

The bus in five steps: a decomposition, a breakdown, and progressive insight #134

jschoubben referenced this pull request

2026-09-26 17:03:28 +00:00

Give 0115 a home, and match its batch's status — main is failing both checks #135