Six modules name no /var/lib: the root is a place, the maps reference it #104

2026-09-26T16:20:54Z

jschoubben commented

2026-09-26 16:20:54 +00:00

The state directories say place: "." — the assignment's own root — and every bind, secret, own-secret, receives and grants path references it as ${dir:state}/…; grants directories that are their own resources are placed by id. gitea's two coincidence strings from the first pass (${dir:data}base.json, resolving correctly by pure concatenation) are spelled honestly now.

What still says /var/lib is inside containers — the software's contract — or under /var/lib/mesh, the mesh's own plumbing, which the requirements unification absorbs next. Every resolved path is byte-identical to what runs; landing this is a no-op on the node. Needs mesh-controller #70 deployed (it is).

The state directories say `place: "."` — the assignment's own root — and every bind, secret, own-secret, receives and grants path references it as `${dir:state}/…`; grants directories that are their own resources are placed by id. gitea's two coincidence strings from the first pass (`${dir:data}base.json`, resolving correctly by pure concatenation) are spelled honestly now. What still says `/var/lib` is inside containers — the software's contract — or under `/var/lib/mesh`, the mesh's own plumbing, which the requirements unification absorbs next. Every resolved path is byte-identical to what runs; landing this is a no-op on the node. Needs mesh-controller #70 deployed (it is).

jschoubben added 1 commit 2026-09-26 16:20:55 +00:00

Six modules name no /var/lib: the root is a place, the maps reference it afdd149ab7

The state directories say place "." — the assignment's own root — and
every bind, secret, own-secret, receives and grants path references it
as ${dir:state}/…; grants directories that are their own resources are
placed by id. gitea's two coincidence strings from the first pass
(${dir:data}base.json — resolving correctly by pure concatenation) are
spelled honestly now. What still says /var/lib is inside containers —
the software's contract — or under /var/lib/mesh, the mesh's own
plumbing, which the requirements unification absorbs next. Every
resolved path is byte-identical to what runs; landing this is a no-op
on the node, and the converter checks its own boundaries this time.

jschoubben merged commit 705ceec1e7 into main

2026-09-26 16:21:01 +00:00

jschoubben deleted branch feat/six-modules-name-no-var-lib

2026-09-26 16:21:01 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#104