Thanks for your comments and the earlier outline. Iteration it is. We can hash out the labels as we go along.
Regarding the labels: Let's work on a word change here. Instead of 'controlled' what feeling do you get about 'approved'? It's not so rigid. The idea is to let folks know that the imprimatur of some body has looked over and agreed with the contents/intent of the page. The label bestows slightly more weigh, by virtue of the review status, than a random page written by a developer. Think about your trust level for random web pages vs web pages on a respected site.
I agree that the Project controlled documents need to be archived in Docushare (or follow-on). But we have many documents which don't rise to that exacting standard yet inform the Developers about management's expectations on them. For example,the TCT decided some years back to allow upreving of selected 3rd party products to occur on a semi-annual period without reapproval by the TCT (if they first verified the uprev worked,etc). This is not an LDM controlled rule but an internal DM Policy. (Under the new division of labor, it might now be a SAT Policy instead of a TCT Policy.)
Regarding 'living', 'versioned', 'archived' - I think we only need one designating 'versioned' to indicate that a particular page is anchored to a specific Release. We wouldn't need to designate 'versioned' on the various versioned Spaces we have; that would be redundant. Dick should respond with his sentiments on this, too.
I view 'curator' as the person who is responsible for periodically looking over their document fiefdom for obsolete pages which either should be updated or removed. Confluence has nice searching facilities for searching on page labels. However, I wouldn't want to inhibit anyone who was willing to update a page's content on their own. I believe it's a 'Buck stops here' concept for Dick. So when he notices a disreputable page, he knows to whom to talk in order to get it fixed.
I'm moving this Issue into Done.