Ability to create and share sub-projects between organisations

[pospi]

In #46 we've discussed the need to be able to merge projects together; the other side to this coin is being able to split projects apart.

It is highly likely that the appropriate way of implementing this is to dynamically deploy Holo-REA DNAs as sub-networks of the main collaboration space they are being created within. This provides for fractally composable project collaboration spaces.

Other orgs or participants outside of the "main" collaboration space could be invited to the new project sub-network after it has initially been created, via whatever role-based capability management abstractions we might provide (see #61). This would enable projects to be shared between groups.

The necessary components for this will include stuff like:

• dynamically generating Holochain app specs and building DNAs on the fly
  • part of this will necessitate dynamic injection of zome configuration properties
• optional inheritance of capabilities and permissions from the parent DNA
  1. public sub-projects: when deployed with this option, the new project is accessible even to others outside of the parent collaboration space.
  2. permissioned, discoverable sub-projects: some registry logic would need to be present in the parent DNA, which sub-projects would register their network ID into so that other users in the parent collaboration space can discover and join the sub-project.
     • sub-projects may or may not bind to an agent relationships zome in the parent network in order to synchronise access roles and capabilities for the sub-project when eg. users are added to the parent network's groups.
  3. private sub-projects: in these cases, no registry is needed and the initial zome configuration (eg. agent ID whitelist) is configured to entirely decouple the sub-project from the parent DNAs. After initialising, the sub-project functions as its own autonomous entity.