valueflows docs
git clone
Log | Files | Refs | README

commit 016a1217cdb703e912a132274b3e31547a7a2b5c
parent e94ebdd7d6347c5ef3fe3a8d7600ca40a831d23f
Author: Lynn Foster <>
Date:   Sat, 19 Jan 2019 17:29:13 -0600

Merge pull request #406 from elf-pavlik/illustrate-flows

additional figures explaining flows
Aassets/flows.png | 0
Aassets/matched.png | 0
Mdocs/introduction/ | 13+++++++++++++
3 files changed, 13 insertions(+), 0 deletions(-)

diff --git a/assets/flows.png b/assets/flows.png Binary files differ. diff --git a/assets/matched.png b/assets/matched.png Binary files differ. diff --git a/docs/introduction/ b/docs/introduction/ @@ -19,6 +19,19 @@ Commitments describe potential future event which involved agents already agreed Economic event describes past event, something already observed, never some potential future event. +## Timeline, plans and observations + +Figure below shows that Economic Events have to be observed and for that reason only appear as records of the past. Future plans get represented with Intents and Commitments. + +![flows]( + +## Matching Intents + +Often agents will start their plans independently and record their initial intents. Later once they make a Commitment with other agent, it will represent a specific shared part of their plans. For that reason any Commitment can result in Satisfaction of providing agent's Intent as well as Satisfaction of receiving agent Intent. + + +![matching]( + ## Granularity Intents, Commitments, and Economic Events can occur at any granularity that is needed or for which data can be obtained. So they primarily are used for all operational needs, but can also be used at higher levels for analytical and high level planning needs for communities or regions, for example.