Create a basic multi-player browser game (simpler than the MS Hearts interface), then ask for people to play it. Make the game robust enough to test your ideas, yet simple enough that participants can quickly learn the rules and play the game properly - a condition that still allows for great complexity, depending upon the participants.
Run many trials, contrast the results of the games with your predictions, and revise or discard your hypothesis as necessary. Slowly introduce confounds into your game to test its real-world viability. Ultimately run a long-term game (a couple of weeks or so) in a real world setting as a mock trial. Scale up from there.
In other words, experiment. Prove the feasibility of the idea then build around it. Perhaps the above isn't even necessary; try your best to falsify the idea with the least possible amount of resources, I believe 'twas recommended. The above suggests one manner in which that may be accomplished.
Or something like that1. As per this article on Control Markets I am looking to experiment with them. This requires an organization of some sort. This post is my first step to the creation of the organization.
My skills are in technology and not UI or people particularly. So I have mainly been doing what I know2, working around my day job.
So I decided it probably wasn't the best path, I was likely to get distracted and lose focus by myself. So other people would be useful.
There are three rough ways this can be attempted:
So what is possible with people from lesswrong? And which would people advise? Or is there a different way to attack this problem.
I've thought about kickstarter, but I don't think it is within the ToS. Also I would want a decent demo/visuals before trying this style of thing.
I suppose there is also.
1 I would want to use a kitty for a logo if we went with this name. This is probably why I shouldn't be allowed to make these sorts of decisions.
2 I've been noodling around with a django backend using tastypie to make a restful API, I was thinking about using AngularJS on the client (which I would need to learn). Still needs a lot of work. I also have a bad habit of wanting to make it highly available/scalable and other such things that aren't appropriate at this point.