We will have the idea of 'required' metadata in 1.3. It will be possible to have "incomplete" objects in the repository if they don't have all their required properties. The web client will enforce (as much as is possible in a web application) the collection of required fields - there will also be an additional rule trigger that can be used for incomplete objects (to route it to collect the metadata, for example).
The complexities come both from dealing with content coming from interfaces that have no understanding of collecting additional metadata (FTP etc) and from having aspects. It's possible to add an aspect with 'required' properties at anytime, so the idea of enforcing data collection at create time doesn't work.
Hopefully that makes sense!
Cheers
Paul.