s/Our converter from Pydantic/The converter from module options to JSON schema/
Whereas the core abstraction in Fediversity is a NixOS configuration module, a more full-fledged example architecture of the web host use-case we aim to support would be as follows. VMs in question run Fediversity to offer our supported applications. The diagram shows an example of how different components could be fit together, based on what Fediversity offers as a framework:
Yes, ugly but we need to keep pushing this along until we figure out the rest of the data flow
Also renaming existing items is really confusing, we we want things changed just add new deliverable identifiers
We can rename the workpackage I guess, but we can't remove past items since they have been done.
I don't think we can remove the publicity things, also they've been done and keep getting done so it's worth showing
