Difference between revisions of "Transfers between ventures"
m (Sensorica-wiki moved page Value transfer between ventures to Transfers between ventures) |
|||
| Line 1: | Line 1: | ||
| − | This doc is a deeper reflection and an attempt to model exchanges between [[ventures]] within an OVN. | + | This doc is a deeper reflection and an attempt to model transfers (could be exchanges) between [[ventures]] within an OVN. |
| + | |||
=Our Material used in this attempt= | =Our Material used in this attempt= | ||
| Line 9: | Line 10: | ||
=Introduction= | =Introduction= | ||
| − | At this moment there are 3 ways to transfer value from one [[ | + | At this moment there are 3 ways to transfer value from one [[venture]] to another: |
| − | # Through child-parent relationships between | + | # Through child-parent relationships between [[venture]]. |
# Through relations between [[resources]], which are created by users when they log [[contributions]] (Ex. citations, use or consumes). | # Through relations between [[resources]], which are created by users when they log [[contributions]] (Ex. citations, use or consumes). | ||
# [[Recipes]] (to be explored...) | # [[Recipes]] (to be explored...) | ||
| − | [[ | + | [[Ventures]] are nodes nodes in a [[contribution accounting system]]. They are the lowest-level structured in which efforts ([[contributions]]) can be evaluated. Incentives appear at the [[venture]] level, where goals appear, therefore the [[value equation]] is applied at the [[venture]] level too. |
However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. Resources created by one process can be used within a different process. Processes can belong to different [[ventures]] or [[projects]], therefore value passes between [[ventures]] or [[projects]] at the resource level. | However, [[contributions]] are made to a [[processes]], which uses and creates [[resources]]. Resources created by one process can be used within a different process. Processes can belong to different [[ventures]] or [[projects]], therefore value passes between [[ventures]] or [[projects]] at the resource level. | ||
Revision as of 03:13, 20 October 2021
This doc is a deeper reflection and an attempt to model transfers (could be exchanges) between ventures within an OVN.
Our Material used in this attempt
Use the vocabulary extracted by Bob (open Doc)
Use the Value System doc. Use also other docs in the SENSORICA/INFRASTRUCTURE folder.
Introduction
At this moment there are 3 ways to transfer value from one venture to another:
- Through child-parent relationships between venture.
- Through relations between resources, which are created by users when they log contributions (Ex. citations, use or consumes).
- Recipes (to be explored...)
Ventures are nodes nodes in a contribution accounting system. They are the lowest-level structured in which efforts (contributions) can be evaluated. Incentives appear at the venture level, where goals appear, therefore the value equation is applied at the venture level too.
However, contributions are made to a processes, which uses and creates resources. Resources created by one process can be used within a different process. Processes can belong to different ventures or projects, therefore value passes between ventures or projects at the resource level.
Ventures or projects are modeled as static structures. Value is modeled as flows. Processes belong to the flows: they are transient, come and go, are scheduled to happen and then documented as what did happen. The processes are where the actual value exchanges happen.
For example, the Mosquito venture will last a long time. During that time, many Mosquitos will be created by many processes. The designs of the Mosquitos and the methods of making them may change many times, but the Mosquito venture will be the context for all of them.
Preliminary considerations
Categories of ventures
It is important to separate ventures into categories because they can be so different that they need special treatment within the contribution accounting system. Moreover, different types of ventures or projects attract different types of individuals and tend to create specific cultures around them. That can lead to different group decisions in terms of evaluations of contributions and the benefits distribution algorithm. See more on the Venture page.
Papers to get and read
Managing collaborative R&D projects development of a practical management tool