Can we start by talking about what it does more than just "deploys shrinkwrap archives?"
I assume the key capability it is trying to add to the deployer process is the ability to reuse application provided (already loaded) classes, with metadata pointing at them?