valueflows docs
git clone
Log | Files | Refs | README

commit 07e59fe3eafaed23f0f251f838757d47a7bcf738
parent dfa617f6e48c6461172b300540fc585882b5952d
Author: Lynn Foster <>
Date:   Fri,  9 Oct 2015 11:23:01 -0500

Merge pull request #47 from valueflows/principles

add principles from wiki to
Diffstat: | 20++++++++++++++++++++
1 file changed, 20 insertions(+), 0 deletions(-)

diff --git a/ b/ @@ -0,0 +1,20 @@ +# Value Flows Principles + +These principles are about the model behind the vocabulary. + +1. The model must enable collaboration between different people in different organizations using different software on different platforms using different human and programming languages. +2. 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. +3. 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. +4. 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. +5. 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. +6. 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. +7. The model must support non-business-as-usual organizational forms and economic relationships in addition to traditional business organizations and relationships. +8. 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