Operator's insight: the login identity ("who you and I are on each node") is crucial mesh information, and something must own ~/.ssh inside the nox mesh. Confirmed the gap in code — the node record has no account field, and no nox module writes under a home. Proposes two paired additions: the operator account as a node fact, and a home-scoped resource class (the ~/ mirror of ADR 0112's /var/lib placement, owned by the account), with the login key staying the operator's per ADR 0051. Captures the open questions (one vs many accounts, where the key lives, the sshd boundary) rather than deciding them. Not urgent/not blocking — HAL's generators still run as substrate; load-bearing at node-by-node retirement.
Operator's insight: the login identity ("who you and I are on each node") is crucial mesh information, and *something* must own `~/.ssh` inside the nox mesh. Confirmed the gap in code — the node record has no account field, and no nox module writes under a home. Proposes two paired additions: the operator account as a node fact, and a home-scoped resource class (the `~/` mirror of ADR 0112's `/var/lib` placement, owned by the account), with the login key staying the operator's per ADR 0051. Captures the open questions (one vs many accounts, where the key lives, the sshd boundary) rather than deciding them. Not urgent/not blocking — HAL's generators still run as substrate; load-bearing at node-by-node retirement.
The mesh models machines but not the people on them — a node record
holds no username, and no module places anything under a home. So who
you are on each node (jochens/ace/jochen) is unknown to the mesh, and
nothing owns ~/.ssh, dotfiles or ~/.config. HAL knew it; the nox mesh
dropped it. Proposes the account as a node fact and a home-scoped
resource class (the ~/ mirror of ADR 0112's /var/lib placement), with
the login key staying the operator's (ADR 0051). Not urgent — HAL's
generators still run — load-bearing at node-by-node retirement. Found
generating ~/.ssh/config from HAL's registry, which nox has no
equivalent for.
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.
Operator's insight: the login identity ("who you and I are on each node") is crucial mesh information, and something must own
~/.sshinside the nox mesh. Confirmed the gap in code — the node record has no account field, and no nox module writes under a home. Proposes two paired additions: the operator account as a node fact, and a home-scoped resource class (the~/mirror of ADR 0112's/var/libplacement, owned by the account), with the login key staying the operator's per ADR 0051. Captures the open questions (one vs many accounts, where the key lives, the sshd boundary) rather than deciding them. Not urgent/not blocking — HAL's generators still run as substrate; load-bearing at node-by-node retirement.