What are the requirements for OVN infrastructure?

A related question, which was mentioned by @derekrazo , is how should this stuff be carved into something like modules. Derek wants tiny ones.

Valnet software is huge. We're experimenting to find out how this stuff needs to work, what are the operational requirements, learning a lot and changing the software continuously. We don't know which joints to carve it at yet.

If you understand our model (Resources, Events and Agents), could we tiny it down to the point where every Agent had their own server and just federated with all of the associated agents? If so, what features would be required by an individual agent?

And what if that agent was a network or a worker cooperative (which are all agents in our new networks-of-networks model)?

And what would it take to do this?
https://github.com/valnet/valuenetwork/wiki/Value-Streams

Is this the place for a serious and detailed discussion about how to modularize? Enspiral lists Small as one of their requirements for their open-app project. We (Mikorizal) are not small, but we would be happy to discuss small pieces with Enspiral and others (see the metamaps listed above which resulted from a previous discussion).

Or should we set up a new forum, maybe Small Pieces Loosely Joined? Or something else entirely?

Or does nobody have time and/or interest? Or just too soon?

@joshuavial @simontegg @derekrazo @josefdaviescoates

Best place to discuss this would be in the technical group of App Ecosystem - https://www.loomio.org/g/B2JpoztU/app-ecosystem-technical

Will send you an invite.