SODOTO Contract

Here Marc and Zach explore the logic of a SODOTO token for Relocalize Creativity, implemented in the FedWiki and Planet Nine infrastructure.

Assessment of Agreement

AGREEMENT

* The Doers > Kerry > Christo > Liv

* Modeling Tools for Neighborhoods > CLD > Sofi-VSM > Schema Diagram > Social Action Tetrahedron CLD > Neo4j and Solo Super Collaborator > Social System (BGTE) > EIP Stage Sketch > Six Questions > Cynefin > Process Mapping and Linkage Mapping > Value Stream Mapping & A3 Problem Solving > OPM (OPCloud) > Vester's Sensitivity Modeling (in 9 parts)

# Context: (Background of Understanding)

* Neighbors can better improve their situation when they can see the systems they are enmeshed in and see how they can better use or change those systems. We refer to models of neighborhood situations as diagrams or cave drawings. They are models.

# CUSTOMER SCENARIO: (Value to be delivered to end customers)

* In order for it to work people who know how to use tools must be able to teach others to use them and be paid back by the new user taking some of the responsibility for teaching, that otherwise remained with a very few teachers.

* A debt is incurred by the learner (seeing one). Some of that debt is retired when the learner uses the tool (doing one) to the satisfaction of the teacher (teaching one). The remainder of the debt is retired when the learner teaches someone else to how to use the tool and they in turn use it (doing one) to the satisfaction of the original teacher.

* Each step in this chain can be recognized by authorizing the creation of unique tokens memorializing the creation and retirement of such debts. > Ideally (eventually) each token indicates not only the type of value (denomination) created (taught, learned, used) BUT ALSO the content, time, participants, location, and specific model illustrated.

* Teachers can accumulate Teach One Tokens (acknowledged by the students). Students can accumulate See One Tokens authorized by their teachers.

* Teachers can accumulate Repayment Tokens from students who satisfactorily demonstrate their skill in using the tool. Each Do One Token is created simultaneously with a Repayment Token when the teacher certifies the doing as satisfactory. The doer gets the DO ONE token, their teacher gets the Repayment Token > (If a teacher accumulates disproportionately more Teach One Tokens than Repayment Tokens, they have failed as teachers. Ideally every Teach One Token will generate at least three Repayment Tokens. It is the Repayment Tokens that signify real value to the ReLocalize Creativity undertaking.)

* The final value that repays the teacher occurs when the student has taught second student and that student has used (Do One) the learned tool to the satisfaction of the first student. When this act is certified by the first student: the second student receives a See One token, the first student receives an Taught One token, the first teacher receives a second order Repayment Token. It probably makes sense for the Repayment Token to be dependent upon the first teacher certifying the second students work (use of the tool). This will reinforce the learning for the first student.

* These tokens memorialize the creating of valued skills, not the ownership of property. They are the Creative Currency of ReLocalize Creativity.

* I do not yet see a need nor an opportunity to exchange SODOTO token, though they could be used a tickets for access to other places and events and opportunities.

* NOTE: Fiat currency is used for exchanging value, generally related to property or labor. I am unclear where the creation of value or the creation of knowledge is recognized with fiat currency. > The creation of currency is done by banks though the loaning of currency at interest caluclated to be greater than the risk of not having the newly printed currency returned. Since the new currency was made out of thin air, I fail to see the risk other than the cost of transferring accounting and collecting.

That said, in the case of the Fledge, Fledge Dollars (Ethereum currency) could be "paid" to any party for any step in the teaching, learning, doing chain. I strongly prefer to keep the payment system distinct from the certification system.

* Fairness * Reciprocity * Accountability * Anti-hoarding. anti-stasis * Transparency * Visibility (of systems)

# Parties to Agreement: ME-ME Customer--Supplier Pairs (with goals and metrics)

* Teachers of tools > Kerry taught Christo Causal Loop Diagramming

* Learners and users of tools > Christo saw Kerry teach CLD tool > Christo taught Liv to use the CLD tool to Kerry's satisfaction > Liv used the tool to the satisfaction of Kerry and Christo

# Potential Benefits (monetary and more)

* Teachers will realize that their efforts are having the desired effect in the world.

* Learner will be better able to address problems * People in neighborhoods will become skillful problem solvers and innovators--becoming less susceptible to the whims of outsiders.

* Local economies will flourish enhancing the lives of locals and their adjacent communities.

* If we do this well, the province of every skill will be traceable (via Neo4j queries)

# Conditions of Satisfaction between Pairs: Goals with metrics (time specified)

* The teacher will teach to the satisfaction of the learner. * The teacher will support the learner in their first uses of the tool and in their first teaching of the tool.

* The learner will make their best effort to learn to use the tool and practice its use. * The learner will make their best effort to recruit and teach others to make use of the tool to a high standard (at least that of their own teacher).

* Each certification step should require the declaration of satisfaction by the two or three parties involved. In other words the agreement (contract) of certification must be signed by the two or three parties involved to issue the tokens of certification.

This diagram represents the full extent of tokens considered. We certainly can begin with only two events and their four tokens, e.g. both DO ONEs by the first and the second students.

*

# Value Sharing by Participant by Stage:

*

# Support Services (Microsystems)

*

*

.

This is text in the new plugin. You can *double-click* to edit it too.

For more context see Basic RenDanHeYi

_Click on the node labels to further explore the diagram._

digraph { overlap = false; splines=true layout = dot 0 [label="Micro Enterprise", shape=oval, style=dashed, color=green3, penwidth=6, fillcolor=green tooltip=""] 1 [label="Customer" shape=egg, color=bisque3 penwidth=6 fillcolor=white tooltip=""] 2 [label="Problem" shape=box, color=red penwidth=6 fillcolor=white tooltip=""] 3 [label="Solution\n(Customer\nScenario)" height=1.1 margin=0.1 shape=signature, color=green penwidth=6 fillcolor=yellow tooltip=""] 4 [label="Reward" shape=box, color=gold penwidth=6 fillcolor=white tooltip=""] 5 [label="Ecosystem\nMicro-Community" shape=oval, color=green3 style=dashed penwidth=6 fillcolor=white tooltip=""] 6 [label="P&L" shape=note, color=black penwidth=2 fillcolor=white tooltip=""] 7 [label="Ecosystem\nAgreement\n('Contract')" height=1.2 margin=0.2 shape=signature, color=green2 penwidth=4 style=filled fillcolor=black fontcolor=white tooltip=""] 8 [label="Principles" shape=triangle, color=black penwidth=6 fillcolor=white tooltip=""] 9 [label="Goal" shape=rarrow, color=pink penwidth=3 fillcolor=white tooltip=""] 10 [label="Base Pay" shape=box, color=gold penwidth=6 fillcolor=white tooltip=""] 11 [label="Bonus" shape=box, color=gold penwidth=6 fillcolor=white tooltip=""] 12 [label="Industry\nPlatform" shape=oval, color=blue, penwidth=6, style=dashed fillcolor=white tooltip=""] 13 [label="VAM\nAgreement\n('Contract')" height=1.2 margin=0.2 shape=signature, color=green2 penwidth=4 style=filled fillcolor=black fontcolor=white] 14 [label="Unit\nIncubation\nAgreement\n(Contract)" height=1.5 margin=0.2 shape=signature, color=blue penwidth=4 style=filled fillcolor=black fontcolor=white tooltip=""] 15 [label="Shared\nServices\nPlatforms" shape=signature, style=dashed, shape=oval, color="#25a0e7" penwidth=6 fillcolor=white tooltip=""] 15->7 [style=dashed color=black penwidth=4] 12->14 [style=dashed penwidth=4] 14->5 [style=dashed penwidth=4] 13->0 [style=dashed penwidth=4] 1->2 [label="" labeltooltip="" ] 0->3 [label="" labeltooltip=""] 3->1 [label="" labeltooltip=""] 0->2 [label="" labeltooltip=""] 1->4 [label="" labeltooltip="" color=green2 penwidth=3] 4->0 [label="" labeltooltip="" color=green2 penwidth=3] 0->5 [label="" labeltooltip=""] 0->6 [lael="" labeltooltip=""] 0->7 [label="" labeltooltip="" style=dashed color=green2 penwidth=4] 8->5 [label="" labeltooltip=""] 0->8 [label="" labeltooltip=""] 7->5 [label="" labeltooltip="" style=dashed penwidth=4] 0->1 [label="" labeltooltip=""] 0->9 [label="" labeltooltip=""] 7->10 [label="" labeltooltip="" color=green2 penwidth=3] 7->11 [label="" labeltooltip="" color=green2 penwidth=3] 6->10 [label="" labeltooltip=""] 6->11 [label="" labeltooltip=""] 9->6 [label="" labeltooltip=""] 9->7 [label="" labeltooltip="" ] #12->5 [label="" labeltooltip=""] #7->12 [label="" labeltooltip="" color=green2 penwidth=3] }