expand_less
There are a number of concepts related to this that need to be kept clear so their relationships can be effectively used in systems design. From the [[XPFL]] context, we have the idea of "agent class" (moving from game/play/player to pattern/action/agent language for this) and we are working on Eric's implementation of [[Membranes]] [[Set]] as the way naming and binding is controlled within Flowplace processes. The [[Membrane+Set]] is used to define the processes by which games are administered, the actions in this pattern bind [[Agents]] to agent classes in active pattern contexts.
We have noticed a particular pattern for this that closely matches the organizing principles of open communities. We see this here with [[http://www.wagn.org/wagn/Wagn_Modules+architecture|wagneers and other participant types]], and it is a general pattern for a meritocracy where skills and interest determine where one lands in an organization or network. This is not the only possible semantics that is supported by membranes, but it is a key one for our communities and FlowPlace in general.
{{+Spheres|size:full}}
Participant Types at FlowPlace
The question arises as to whom we are designing these tools for. Ultimately we want to deploy these systems in support of many communities of practice and most of these are expected to be users of currencies. But we don't really have completed currency systems in place, so our work is often addressing the spaces of currency designers, technologists and process architects who are working to create practical flow systems for direct use by their communities.
Tags:
{{+tags|item:link}}
{{+discussion|open}}
We have noticed a particular pattern for this that closely matches the organizing principles of open communities. We see this here with [[http://www.wagn.org/wagn/Wagn_Modules+architecture|wagneers and other participant types]], and it is a general pattern for a meritocracy where skills and interest determine where one lands in an organization or network. This is not the only possible semantics that is supported by membranes, but it is a key one for our communities and FlowPlace in general.
{{+Spheres|size:full}}
Participant Types at FlowPlace
The question arises as to whom we are designing these tools for. Ultimately we want to deploy these systems in support of many communities of practice and most of these are expected to be users of currencies. But we don't really have completed currency systems in place, so our work is often addressing the spaces of currency designers, technologists and process architects who are working to create practical flow systems for direct use by their communities.
Tags:
{{+tags|item:link}}
{{+discussion|open}}