ADR 0252: a module puts an account in a group, and the mesh says when a new login is needed #201

2026-10-08T10:04:57Z

mesh-admin commented

2026-10-08 10:04:57 +00:00

Resolves issue 247 (a module cannot put the operator's account in a group).

ADR 0252: a module declares the account as a user resource with the group and nothing else of it; such a resource keeps its written place (after the package that makes the group); the node-engine records and gives back only groups it added, never one the account was in before, and not while another declared resource asks; it says relogin needed as the module's resource of kind account until the account's running session has the group. Options rejected: a new resource kind (refused whole by every older node-engine), a contribution to a seat, the hand step.
To-be 41 WP6: the work in mesh-host, mesh-controller and mesh-catalog, its proof and order.
Issue 247: resolved, with the correction that the controller already allowed a second module's groups since 2026-10-04, and the answers to its three open questions.
Glossary: account group (Placement), relogin needed (Health and repair), and membership as a homonym.

Code: mesh-host #54, mesh-controller #139, mesh-catalog #125. merge-check.sh passes locally.

Resolves issue 247 (a module cannot put the operator's account in a group). - **ADR 0252**: a module declares the account as a `user` resource with the group and nothing else of it; such a resource keeps its written place (after the package that makes the group); the node-engine records and gives back only groups it added, never one the account was in before, and not while another declared resource asks; it says *relogin needed* as the module's resource of kind `account` until the account's running session has the group. Options rejected: a new resource kind (refused whole by every older node-engine), a contribution to a seat, the hand step. - **To-be 41 WP6**: the work in mesh-host, mesh-controller and mesh-catalog, its proof and order. - **Issue 247**: resolved, with the correction that the controller already allowed a second module's groups since 2026-10-04, and the answers to its three open questions. - **Glossary**: *account group* (Placement), *relogin needed* (Health and repair), and *membership* as a homonym. Code: mesh-host #54, mesh-controller #139, mesh-catalog #125. `merge-check.sh` passes locally.

mesh-admin added 1 commit 2026-10-08 10:04:57 +00:00

ADR 0252: a module puts an account in a group, and the mesh says when a new login is needed

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

3449775cb6

Issue 247 left adding the operator's account to a daemon's group a sudo step by hand. Decide that
a module declares it with the user resource's groups, that the mesh gives back only what it added,
and that the node-engine says relogin needed; amend to-be 41 with WP6 and resolve the issue.

mesh-admin commented

2026-10-08 10:05:18 +00:00

Delivery novox/hq@3449775cb60f — delivered since 2026-10-08T11:05:36Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-08 10:05 (new) → proposed (announced): novox/hq#201's head announced
2026-10-08 10:06 proposed → checked (checked): the verdict names this commit
2026-10-08 10:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 11:05 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 11:05 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@3449775cb60f` — **delivered** since 2026-10-08T11:05:36Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 10:05 (new) → proposed (announced): novox/hq#201's head announced - 2026-10-08 10:06 proposed → checked (checked): the verdict names this commit - 2026-10-08 10:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 11:05 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 11:05 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin merged commit 7879ade66f into main

2026-10-08 11:05:12 +00:00

mesh-admin deleted branch decision/0252-a-module-puts-an-account-in-a-group

2026-10-08 11:05:12 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#201