(sorry for starting a new thread when this was being discussed elsewhere, but we were threadjacking it, and I think all concerned, or at least most concerned will be glad to see that thread drop down the latest topic list-Foz)
The basics:
A) The article can be placed under BLP-LOCK by any uninvolved administrator. When an administrator places an article under this policy, they must either refer to an existing OTRS ticket, or submit one, and detail why such action is necessary in that OTRS ticket.
B ) If an OTRS volunteer agrees that the article should be placed under BLP-LOCK, the article will be stubbed down to a bare-bones situation (just bare facts, no controversial information), and fully-protected for a period of a MININUM of six months (this can be permanent).
C) During this BLP-LOCK status, the only edits that should be made are those via {{editprotected}} requests that have full-consensus on the talk page. Any information that not reliably sourced should not be added to the article, even with consensus. While a subject of the article does not get an automatic veto over information being added to the page, administrators who handle BLP-LOCK editprotected requests should be fully aware of the BLP policy and judge accordingly.
This is actually fairly close to the Stable Versions idea we've been promised for eons going forward.. It reduces a major part of the reason that folks (here and elsewhere) are upset about BLP: That any "child with a computer" can vandalize it, and then these vandalizations are available in the history forever.. and for folks that don't have people watching/OWNing the article, these vandalizations can persist for a period of time until caught. Instead, the article grows in a more controlled manner.
The reason for thinking that the OTRS ticket is necessary.. I'm not sure this is necessary or a good idea for ALL BLP articles, but if an article needs BLP-LOCK, then it should have above-normal levels of attention paid to it, and OTRS is one way to do that. I know that the problem is that OTRS can be overwhelmed at times, I'm willing to put my money where my mouth is on it, and work OTRS/BLP-LOCK if it goes through.
Also, on a strictly personal level of thought.. if a subject complains to WP via OTRS, this should be a standard option (to BLP-LOCK their article) going forward. It's bad enough if a subject needs to email us once if there's problems with their article. We shouldn't have to make then continually monitor their article.