fediversity.md

@@ -436,55 +436,13 @@ To ensure reproducibility, we also offer Nix packaging for our software.
 
 To reach our goals, we aim to implement the following interactions between [actors](#actors) (depicted with rounded corners) and system components (see the [glossary](#glossary), depicted with rectangles).
 
-```mermaid
+![](https://git.fediversity.eu/Fediversity/meta/raw/branch/entity-relations/architecture-docs/interactions.svg)
-flowchart
 
-  user(user) --> |use| deployment
+### Data model
 
-  configuration -->|deploy| deployed
+The data model used for migrations is as follows:
-  devs(developers) --> |maintain| fediversity
 
-  fediversity --> |update| provider1
+![](https://git.fediversity.eu/Fediversity/meta/raw/branch/entity-relations/architecture-docs/data-model.svg)
-  subgraph provider1["fediversity setup A"]
-    subgraph panel1[panel]
-      configuration[staged configuration]
-      configuration --> |update| configuration
-      deployed[deployed configuration]
-    end
-    deployed --> |describe| deployment
-    provider-config[runtime config] --> |describe| host
-    provider-config --> |implement runtime interfaces| panel1
-    subgraph host[runtime environment]
-      deployment[applications]
-      state
-    end
-  end
-
-  deployment --> |store| state
-
-  operator(operator) --> |change| configuration
-
-  subgraph provider2["fediversity setup B"]
-     subgraph panel2[panel]
-      configuration2[staged configuration]
-      deployed2[deployed configuration]
-    end
-    subgraph host2[runtime environment]
-      deployment2[applications]
-      state2[state]
-    end
-  end
-
-  operator --> |trigger| migration
-  configuration & deployed & state --> migration
-  migration --> configuration2 & deployed2 & state2
-  provider(hosting provider) --> |maintain| provider1
-  subgraph fediversity[fediversity source code]
-    applications[application modules]
-    backends[runtime backends]
-    config[runtime options]
-  end
-```
 
 ## Break-down of project milestones