I'm looking for ideas here...

Concept: Teams have private collaborative team sites where they do
their work. Occassionally, they will develop a document that should
be made accessible to a wider audience. (ex. IT user guides,
policies, etc.) Rather than manage item level permissions in these
private team sites, the company would like to "publish" these
individual documents to sites open to the general employee
population. Ideally, the users should not have to know the exact
location where the document should be published. That should be
determined via the standard metadata columns associated with all
documents throughout the portal.

Example: a small IT team develops a user guide for an application.
It's a word document under version control. When it's ready to be
published, the team lead submits the doc for publishing. The portal
sees that the document is a User Guide content type managed by IT and
intended for viewing by "All Employees." Based on this, the document
is published to the Employee Resources / IT library as a user guide.

When the team updates the source document, they are prompted to
update the published copy of the document also.

_________________

This is very similar to the Send To capability, although that
functionality is limited to 1 pre-defined choice.

I thought the records center might be a good possibility, given the
routing rules and the ability to define the record center location in
Central Admin. However, with it adding new files for every update
and altering the file names, it would be very difficult to get that
in a state that could be used for this altered purpose.

We could write a custom workflow, I suppose.

OTHER IDEAS???