diff --git a/principles_tech/actor_based_approach.md b/principles_tech/actor_based_approach.md index e69de29..647fd14 100644 --- a/principles_tech/actor_based_approach.md +++ b/principles_tech/actor_based_approach.md @@ -0,0 +1,7 @@ +## OurDigital Self Actor Driven Approach + +![](img/twin_model.png) + +WITH OurTwin, there is an 'actor' driven pattern instead of a model first pattern. In such a pattern, the root model only holds essentials in its database, hence any necessary changes can be applied at the root. + +The model can tap direct into knowledge (how to do certain things) by accessing the 'recipes'. 'Recipes' are the source code that can easily be adapted to any task. By using Domain Specific Language (DSL) it is easy to reuse recipes. diff --git a/problems/painkiller/actor_based_approach.md b/problems/painkiller/actor_based_approach.md index e69de29..647fd14 100644 --- a/problems/painkiller/actor_based_approach.md +++ b/problems/painkiller/actor_based_approach.md @@ -0,0 +1,7 @@ +## OurDigital Self Actor Driven Approach + +![](img/twin_model.png) + +WITH OurTwin, there is an 'actor' driven pattern instead of a model first pattern. In such a pattern, the root model only holds essentials in its database, hence any necessary changes can be applied at the root. + +The model can tap direct into knowledge (how to do certain things) by accessing the 'recipes'. 'Recipes' are the source code that can easily be adapted to any task. By using Domain Specific Language (DSL) it is easy to reuse recipes. diff --git a/problems/painkiller/onion_layers.md b/problems/painkiller/onion_layers.md index c9207f5..3918eff 100644 --- a/problems/painkiller/onion_layers.md +++ b/problems/painkiller/onion_layers.md @@ -23,10 +23,3 @@ The problem here is that individual systems are trying to redo things better, ho One way to go around this has been to use Enterprise Message Bus: Controlling how models talk to each other by pre-defining the messages exchanged. But this does not solve the problem at the root. -## OurTwin Scenario - -![](img/twin_model.png) - -WITH OurTwin, there is an 'actor' driven pattern instead of a model first pattern. In such a pattern, the root model only holds essentials in its database, hence any necessary changes can be applied at the root. - -The model can tap direct into knowledge (how to do certain things) by accessing the 'recipes'. 'Recipes' are the source code that can easily be adapted to any task. By using Domain Specific Language (DSL) it is easy to reuse recipes. diff --git a/problems/social_warming/social_warming.md b/problems/social_warming/social_warming.md index d9e544e..ed70d10 100644 --- a/problems/social_warming/social_warming.md +++ b/problems/social_warming/social_warming.md @@ -1,7 +1,16 @@ +![](img/social_warming.png) + +## +5 billion people in survival mode ![](img/toabondance.png) +## Our Kids define our Future World + +![](img/world_behind.png) + +We are maybe too much focussed on what kind of world we will leave behind, rather than thinking about how we need to raise our kids so that they will treat our world differently. + ## Education is everything