-
Notifications
You must be signed in to change notification settings - Fork 1
Decouple value system(s) from main protocol #138
Copy link
Copy link
Open
Labels
layer:coreRegarding the core protocol (cost tracking, transactional fabric, etc)Regarding the core protocol (cost tracking, transactional fabric, etc)layer:interfaceRegarding interfacing with the outside world.Regarding interfacing with the outside world.project:papertag:cyberneticsFor issues relating to systemic automationFor issues relating to systemic automationtag:economicsRegarding economics: dynamics, costs, incentives, etcRegarding economics: dynamics, costs, incentives, etctype:discussionDiscussion or ideas for future direction, input welcome (don't be shy)Discussion or ideas for future direction, input welcome (don't be shy)
Milestone
Metadata
Metadata
Assignees
Labels
layer:coreRegarding the core protocol (cost tracking, transactional fabric, etc)Regarding the core protocol (cost tracking, transactional fabric, etc)layer:interfaceRegarding interfacing with the outside world.Regarding interfacing with the outside world.project:papertag:cyberneticsFor issues relating to systemic automationFor issues relating to systemic automationtag:economicsRegarding economics: dynamics, costs, incentives, etcRegarding economics: dynamics, costs, incentives, etctype:discussionDiscussion or ideas for future direction, input welcome (don't be shy)Discussion or ideas for future direction, input welcome (don't be shy)
Type
Fields
Give feedbackNo fields configured for issues without a type.
While the main protocol deals with cost tracking, the transactional fabric, bloc organization, resource flows, etc, the value systems that drive these interactions should be split out and put on top of the core protocol.
The interesting bit is that much of the incentives of the cost tracking itself rely on the incentives set up by the value system, so they are almost coupled by default. However, that closes the door for different value systems. The current ones are: