Because we haven't implemented the white paper yet. But we are coding that now and the repo will be opened once we're ready. Meanwhile we did publish the source for the token-weighted voting implementation, see https://blog.colony.io/token-weighted-voting-implementation-... and have opened more than just code, e.g. our employee equity plan https://blog.colony.io/on-creating-a-better-employee-equity-..., the legal reasoning behind a token sale etc.

Do you have an open roadmap? Why not eat your own dog food here and "colonize" development, even if manually?

We run something called a "collaboration network" that is using our early beta product. The product isn't feature complete yet, just task management with a token incentive model. So we're doing early experiments but can't quite pull of more complex ones—yet.

How can you use something that isn't built to build the same thing unless you're using a time machine? I suppose once Colony is in production, you can create a Colony clone using Colony.

It's called bootstrapping, would indeed be interesting if they used there own platform to build it, or run it in a way right now that allows them to migrate to Colony as early as possible. As long as it does not work for there needs, it's not clear why it would be good enough for anyone else.

Currently the software is closed-source, but will be opened up when it's ready.

The whitepaper was just released last week, and the Colony dev team is working on getting a good foundation for the contracts that will comprise the Colony network - once those are ready, it'll be opened up.