On Community, Code and Capital

As I help get Wagn ready as a platform that many will contribute to, the dialog among the team turns to the Community of Code, it is familiar territory, though only tentatively explored and not much implemented in code or practice, it may be time to return to that work with a new perspective in the current context.


When we met on Metacurrency over a year ago, I was interested in prototyping and advancing FlowPlace on Wagn and although the idea didn't get much uptake, that is what I've continued to work towards.  The code on my traits branch is where it all comes together.  In this most advanced code branch in active development we have the final API taking shape in order to support Wagneering of Metacurrency and FlowPlace systems.  I've broken it now with core work on cardnames and settings and a new caching system based on these, but at one point I had the basic idea of a card with a special attachment (a +*sol card) being able to receive a set of data values from a "multi_edit" form.  The final step is to use the new Action API to create a glue module to the Metacurrency flow engine/network.  So what we have is the implementation needs of a Metacurrency implementation driving necessary capacity and flexibility to the Wagn API, and then in turn we will have the Wagneering of Applications level currency systems, Flowplaces, driving towards the need for Metacurrency transport as adapted for Wagn >> Rails >> Ruby.


It seems pretty clear that I'm already creating the most extreme version of the developer use case for Wagn.  None of the tools out there already do what I want, so I started modifying Wagn pretty deeply to do things.  To give those things longevity and permanence in the project, I jumped in and am helping Ethan to actually produce the API, not just for my project needs but for Wagn generally.  That serves my project goals too because the Metacurrency model is a lot like the Wagn model, we expect people to implement them into lots of other projects, and therefore the potential for seemless Object-Oriented itegration between projects is what we need so that they are in-fact as components of more complex applications.  The Core Cards implementation is what will make that possible.  Metacurrency is conceived as an OO glue for many implementation languagues, and putting these together gives a very fliexiby platform for implementation, and one that is very much buildable in incremental ways (pack by pack and currency by currency) and extendable to any modern delivery system (wep-apps, mobile apps, you name it).


Kinds of Market and a New Approach to Capital Formation


In our call, I resisted the language of Market to describe what we want to create.  It isn't that I am opposed to that sort of formation, the development of complex networks of trade and exchange, just that I think it distorts the formation of shared capital.  Wagn and the Wagn developer community we would encourage the emergence of are not served by the desire for individual visibility for its own sake and the path of branding and mass marketting.  The right sorts of markets, the ones that are based on meshworks of relationship and connection that are reflecting in tradeways, not the other way around.


From all the work and dialog we have shared about currencies and organizations, I know that we need to use newly designed currency systems at the core of our.  When we invite professional developers to join us, we want to know who contributed how much.  We want to be able to hire a core staff to administer the organization.  All this requires a mix of conventional currencies and new currencies.  At the core of this system would be currencies that represented investment in the shared asset whether this is cash contributions to pay fees and salaries of the contribution of code and time.  It is made sustainable by the creation of wealth in the application of the shared assets.  If you make money integrating Wagns and Metacurrency and supporting a bunch of organizations in Cloudstore, you both invest (people and money) in the shared asset and pay fees based on how well you have done.


The currency system can be made as complex or integrated as you want because it uses Metacurrency protocols and Wagn implementations from the start.  Some are redeemable or exchangable, some are just a record of your contribution that is never traded away, some have a long term exchange value as a bridge to conventional finantial tools (conventional credit limits and lines of (mutual) credit).


The key to this isn't these system, though.  What is important is the development of mutual trust and shared investment by the practice of building things together.  We don't want to create a complex market of solutions looking for problems, we want to create a tightly integrated vision for a miriad of possibility.










Wheeled by Wagn v. 1.18.1