Rhizamonitor
live

Roadmap

Area runtime

acceptedintention4 leaves, 0 with evidence

Intent

Why this exists

Area runtime: what remains is the whole area, with agent sessions in Rex, adapters, status, machine trust, hosts, actor stamping and Rex extras.

Leaves

4 leaves, 0 with evidence

  • no evidence yet

    Users bring their own agent through a manifest and an optional executable speaking a JSON protocol.

  • no evidence yet

    Each machine says whether it is dedicated or daily, and bypassed permissions run only on a dedicated one.

  • no evidence yet

    The runtime targets a Rex host by name, so moving work to a hub is configuration.

  • no evidence yet

    Optional Rex extras are installed by the CLI.