This VM on one root

This VM on one root: rhiza and nebari registered under one root run by one root daemon service, replacing rhiza-rhiza.service

• no evidence yet

  On this VM ~/code is the root with rhiza and nebari registered (rhiza as self_update_project), rhiza-root.service runs the root daemon, rhiza-rhiza.service is uninstalled, and the rhiza project's machine settings moved from its git config into rhiza.toml.

  AcceptanceOn the VM: rhiza project ls shows rhiza and nebari with nebari's initialised state as it is, systemctl --user shows rhiza-root.service active and no rhiza-rhiza.service, and rhiza health exits 0; the steps and their output are recorded as Evidence.
• no evidence yet

  Once nebari has a model, the root daemon ships a nebari change set while it runs rhiza's, under the one run cap.

  AcceptanceEvidence from the VM: rhiza daemon status at the root shows a nebari run and a rhiza run live under the same root daemon, and the nebari change set's PR merges.

Serves

Rhiza manages and builds several projects on one machine from one root directory: projects are registered under the root, one root daemon builds them all under one run cap and one usage budget, the CLI, web UI and TUI apps show every project and each on its own, and this VM runs rhiza and nebari that way. This VM runs rhiza and nebari from one root under one root daemon service, with the per-repo daemon service gone.

Depends on

Root daemon landed

• 2026-11-06 15:03Proposed
• 2026-11-06 17:29Accepted