Modularity

This is a raw idea. Don't know how far I will be able to take it right now, but I want to lay down a marker. Maybe somebody else can take it farther.

Consider each of the vf: classes or types. Instances of each of those could have a set of functions that do things for and with it.

Just as a GraphQl reference is emerging, it could be accompanied by code modules.

Those code modules could be composed into vf-apps.

We might need to design a bit more about how they could interconnect. Like, vf:protocols.

Then (@fosterlynn says) the classes and functions could appear in UI modules that could be assembled into sentences and network overviews and dashboards.

Then, given an agent-centric architecture, the agents could form agent-centric organizations and select which modules and apps they want to use, and the vf:vocab and protocols could get the apps and the agents to interconnect and communicate.

Thus, also, modular organizations.

Did I go too far here? Or not yet far enough?