DESIRED CONTENT
Here we will not describe the runtime behavior per regional connector, as this well result in a matrix explosion problem (MxN). Most of the region connector specifics will be moved to the framework developer documentation (please refer to the git history, to restore this information), as it is not architecture per se, but implementation information for users working on specific region connectors.
This section should mainly describe the Permission Process Model and how the different parts of EDDIE Framework interact with each other. This includes
- how EDDIE Core enables region connectors via plugins
- how the Permission Facade comes together by combining EDDIE Core and the region connector specific micro-frontends
- ...
Regarding the specific workflows listed at the end of the page. They will still provide a lot of value, as those are the main use-cases of using EDDIE Framework, but we should explain them based on the Permission Process Model (top-down) and not based on the individual region connectors (bottom-up).
Permission Process Model
Overview
The runtime view focuses on interactions among the system's components. The goal of this section is to describe representative and important workflows that occur during the runtime of the system. These workflows are categorized into sections, as shown below.