novox/hq issue 119, ADR 0112, design 27. 28 modules' data directories are placed (place: ".", sub-directories by id, every host-side reference as ${dir:<id>}, own-secrets included). Resolved on the default root every path is the one named before — proven by mesh-controller's TestPlacedDirectoriesKeepTheirPaths over both checkouts (28/28) — so no data moves and no machine's declaration changes. Five directories whose id is not their last segment keep their path as a placement. What the mesh writes for a module under /var/lib/mesh stays literal: hq issue 174.
Rollout check: each machine's plan --json saved before; after the rebuild wave they must be byte-identical.
novox/hq issue 119, ADR 0112, design 27. 28 modules' data directories are placed (`place: "."`, sub-directories by id, every host-side reference as `${dir:<id>}`, own-secrets included). Resolved on the default root every path is the one named before — proven by mesh-controller's `TestPlacedDirectoriesKeepTheirPaths` over both checkouts (28/28) — so no data moves and no machine's declaration changes. Five directories whose id is not their last segment keep their path as a placement. What the mesh writes for a module under /var/lib/mesh stays literal: hq issue 174.
Rollout check: each machine's `plan --json` saved before; after the rebuild wave they must be byte-identical.
Twenty-eight modules' data directories are placed: the root as place ".", a sub-directory named by
its id, and every host-side reference — binds, secrets, own secrets, grants, receives, file paths,
mounts, env-files — as ${dir:<id>}. Resolved on the default root every path is the one the manifest
named before, which the controller's TestPlacedDirectoriesKeepTheirPaths proves over both checkouts;
so no data moves and no machine sees a change. Five directories whose id is not their last segment
keep their path as a placement (novox/hq issue 119, ADR 0112, design 27).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
novox/hq issue 119, ADR 0112, design 27. 28 modules' data directories are placed (
place: ".", sub-directories by id, every host-side reference as${dir:<id>}, own-secrets included). Resolved on the default root every path is the one named before — proven by mesh-controller'sTestPlacedDirectoriesKeepTheirPathsover both checkouts (28/28) — so no data moves and no machine's declaration changes. Five directories whose id is not their last segment keep their path as a placement. What the mesh writes for a module under /var/lib/mesh stays literal: hq issue 174.Rollout check: each machine's
plan --jsonsaved before; after the rebuild wave they must be byte-identical.Twenty-eight modules' data directories are placed: the root as place ".", a sub-directory named by its id, and every host-side reference — binds, secrets, own secrets, grants, receives, file paths, mounts, env-files — as ${dir:<id>}. Resolved on the default root every path is the one the manifest named before, which the controller's TestPlacedDirectoriesKeepTheirPaths proves over both checkouts; so no data moves and no machine sees a change. Five directories whose id is not their last segment keep their path as a placement (novox/hq issue 119, ADR 0112, design 27).