That is fair enough as long as we have a clear understanding of what is a module and what should be a bundle instead. With DavidL we had a continued that discussion on validating the module wiring.
My current idea is to move the XResolver down one layer and make it the "gate keeper" to the modules wiring API. Deployments that contain 'Dependencies' that would result in inconsistent wiring would not resolve and be rejected at deploy time. They can still be modules though. the static wiring in all modules.xml should be verified at build time.