The story for sensitive/proprietary repositories doesn't feel well-fleshed-out yet:

> Radicle supports private repositories that are only shared among a trusted set of peers, not the entire network. These are not encrypted at rest but rely on selective replication and are thus completely invisible to the rest of the network.

There's no structural separation of public / private repositories; this is one bug or fat-finger away from a leak.

I was looking into how to get a radicle node running, but connected to only my own devices.

You can't seem to start the radicle node without it automatically connecting to the (generously provided) global shared seed nodes, and you can't examine/change the config without starting the node (at least with rad subcommands).

If you do `rad auth` and then delete the four seed addresses from ~/.radicle/config.json before starting the rad node, it helpfully re-adds them on startup:

  [...]
  INFO  node     Opening node database..                                                                                                                                                                           
  INFO  node     Address book is empty. Adding bootstrap nodes..                                                                                                                                                   
  INFO  node     4 nodes added to address book
  [...]

(It doesn't add the bootstrap nodes if I instead add a seed "<randomDID>@10.254.254.254:8776".)

Is there a guide to using Radicle like one might use Fossil within a small company / within a small group of people (disconnected from the iris/rosa radicle.network seeds)?