Author: Lynn Foster <firstname.lastname@example.org>
Date: Thu, 1 Sep 2016 13:24:59 -0500
Merge branch 'master' of https://github.com/valueflows/valueflows.git
3 files changed, 19 insertions(+), 8 deletions(-)
diff --git a/README.md b/README.md
@@ -10,14 +10,25 @@ Or, if that is too many buzzwords, "let's help a lot of alternative economic sof
If you would like to be part of this conversation, please [raise an issue here](https://github.com/valueflows/valueflows/issues), or fork this or any of the related repositories and issue pull requests. You can also pop into our [welcome gitter chat](https://gitter.im/valueflows/welcome) to make comments, ask questions, or introduce yourself!
-## Principles ([long form](https://github.com/valueflows/valueflows/wiki/Principles-for-this-vocabulary))
-- the vocabulary must support coordinating work between different people in different organizations using different software on different platforms using different human and programming languages.
-- the vocabulary must track the flows of resources (value) forwards and backwards.
-- the vocabulary must distribute income (rewards) according to peoples' contributions, regardless of where and when in the network those contributions occurred.
-- the vocabulary must be fractal: it must support high-level views of networks as well zooming in to lower and lower levels of detail.
-- the vocabulary must work at the recipe, planning, and accounting levels.
-- the vocabulary must work for alternative and traditional organizing shapes and economic relationships.
+* The model must enable collaboration between different people in different organizations using different software on different platforms using different human and programming languages.
+* The model must be able to form global networks which can track the flows of resources (values) forwards and backwards. Or maybe it would be better to say "in any direction", but forwards means in the direction of value creation, and backwards means in the direction of return or compensation.
+* Corollary: the model must be able to support value equations that distribute income (rewards) according to peoples' contributions to the creation of the values that generated the income or rewards, regardless of where and when in the network configuration those contributions occurred.
+* The model must also be able to support coordinating work between different people in different organizations. People who are not concerned with rewards may still want to coordinate work.
+* The model must be fractal. It must support global views of networks in aggregate as well as drilling down to lower and lower levels of detail. Those lower levels of detail, for example inside one organization, may require permissions.
+* The model must also work on the Recipe, Plan and Event levels (whatever those get called in the end), where the objects on each level are linked appropriately to the other levels.
+* The model must support non-business-as-usual organizational forms and economic relationships in addition to traditional business organizations and relationships.
+* The model must support systems where all the contributors can get shares of the outcome to allocate as they wish e.g.
+ * contributors to renewable energy coop get kWh of electricity to allocate
+ * contributors to train system get 'km on the railway' to allocate
+ * contributors to food network, get 'food baskets' to allocate
+ * etc.
+* In other words, a group can choose to introduce various monetary currencies into their flows but can also do all the coordination and accounting without introducing such artifacts.
+See also http://discourse.transformap.co/t/principles-for-commoning-transformap-generating-a-global-mapping-commons/518
diff --git a/release-doc-in-process/VF-logo-heading.jpg b/release-doc-in-process/VF-logo-heading.jpg
Binary files differ.
diff --git a/release-doc-in-process/network-elio-cropped.jpg b/release-doc-in-process/network-elio-cropped.jpg
Binary files differ.