Module Development - Prediction Market here we come

I'm about to build a new module and as I started putting "code to .module file" I thought it might be worthwhile to document the process in painfully close detail. Code, architecture decisions, security choices, everything I do.

A lot of people have said something along the lines of "the best parts of dojo screencasts are the parts where people get lost learning how to get out of that state." This would hopefully provide tons of insight into that process of getting lost and finding your way.

The Learning Process

I'd like some input here. I'm thinking a combination of "commit early - commit often", blog posts, Dojo-stylee screencasts, and something else might be good.

The subject matter: Prediction Markets

The ultimate goal is to build a Prediction Market module and perhaps an installation profile. If you are unfamiliar with prediction markets, it's behaves very much like a typical stock market with some small differences. The style of prediction market we will initially build is a "continuous double auction" market based on the Iowa Electronic Markets (IEM). See IEM FAQ for details on that. Understanding of this function is not required to understand module building in general. Of course, if you have ideas on how to make it better as a prediction market module that will help me along ;)

Initial Requirements

We'll need some sort of a banking system, objects to represent the contracts that can be traded, objects for trades themselves, transaction management to match up trades and validate they worked properly (and rollback if not), state management for contracts and trades, graphing, alert messaging, serious thought about scalability, and eventually some ajax to keep the interface snappy.

Are you interested in following along on this project? If so, what means of sharing information do you think would best help you to learn from this project?

Edit: I have now set up Open Prediction Markets to host my blogging/imgaes/ideas on the subject. If you want to stay in the loop on this, that is the place to subscribe to the feed