Rhizamonitor
live

Milestones and backlog

Roadmap

1 milestone · 12 change sets · 1 in backlog

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.

1 accepted
  1. This VM on one root: rhiza and nebari registered under one root run by one root daemon service, replacing rhiza-rhiza.servicedepends on 1 change setacceptedready

Backlog

Not in a milestone

1 change sets
  1. A landing page for Rhiza that shows its name and message, designed from the owner's Claude Design drafts; tabled by the owner for later.proposed—

Umbrella

The rest of the product spec, area by area: each Area change set holds what remains of one area and is split into milestone change sets when it is planned

10 accepted
  1. Area change-sets: what remains is rebasing onto newer landed work, a field-level diff, editing a node as markdown, and notes on a change.accepted—
  2. Area views: what remains is searching the model's text and a change feed since a cursor.accepted—
  3. Area integrity: what remains is anchors to code with fingerprints, commit trailers, drift and reconcile.accepted—
  4. Area repos: what remains is the whole area, with a repo registry, cross-repo links and changes, standards repos and a personal layer.accepted—
  5. Area guide: what remains is installing the guide into AGENTS.md, the reconcile skill, and guide evals.accepted—
  6. Area hooks: what remains is the whole area, with scripts on model events, hook commands, and custom node kinds.depends on 1 change setaccepted—
  7. Area runtime: what remains is the whole area, with agent sessions in Rex, adapters, status, machine trust, hosts, actor stamping and Rex extras.depends on 1 change setaccepted—
  8. Area workflows: what remains is the whole area, with work tasks, workflow definitions and runs, the built-in workflows, overrides, authoring, review and the token ledger.depends on 1 change setaccepted—
  9. Area orchestration: what remains is the whole area, with the daemon, the usage governor, shipping, the inbox, notifications and acceptance policy.depends on 1 change setaccepted—
  10. Area surfaces: what remains is the whole area, with a TUI, a web UI and phone.accepted—