Many of the discussions in Area 51 can be handled by the community processes (vote to close, etc). But proposals that need manual intervention (merges, etc) will be considered and handled much like [feature-requests] and [bugs] in meta.
Discussions start out as proposal-building activities. But if the discussion concludes that external intervention is needed, it should be tagged as a
[change-request] (I will be re-tagging the previous discussions, but feel free to start using this tag now).
I can review change requests and see which have built up a clear consensus. That does not mean that only highly-voted suggestions will get implemented, nor does it mean that every discussion will result in action. I have already found the discussions in Area 51 helpful for weighing in on the issues, but there will be that occasional cantankerous issue where no action is currently warranted. Sometimes proposals simply have to stand on their own and compete.
When particularly difficult or important discussions come up, I can contact proposal followers and link them to the discussion for their input.
When a decision is warranted, I have a set of reserved tags to mark the status of a discussion:
The request has been processed or implemented.
Indicates change-requests that cannot or will not be implemented at the present time.
Meaning "deferred" to the community. Used when the request can (and should) be handled by the EXISTING Area 51 mechanisms. Users are quick to jump in with discussions and requests before trying the mechanisms already in Area 51. For example, many of the requests to close duplicate proposals can be handled through voting; although, sometimes duplicates may be summarily closed if they duplicate existing sites or clearly detract from competing proposals.
Changes are pending some feature, action, or future date.
Indicates that a change may have merit but is still under consideration, perhaps pending a clear community consensus. This interim response will prove useful when an important issue comes up needing further input. I can tag the discussion [status-review], contact the proposal followers by email, and wait for the incoming response.