valueflows docs
git clone
Log | Files | Refs | README

commit 99d1d75fd66c9744ece5bbe7f810957fc53c3a93
parent cc8cb74086d070054d7cd1022da9b1284dfcd7d8
Author: Lynn Foster <>
Date:   Mon, 12 Sep 2016 10:38:04 -0500

added circular economy principle
Diffstat: | 1+
1 file changed, 1 insertion(+), 0 deletions(-)

diff --git a/ b/ @@ -5,6 +5,7 @@ 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 be able to support circular economies, value flows where resources come full cycle to be fed into the same set or other processes so that recycling, re-use, and other ways to encourage resources not becoming waste. 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.