That helped. However, I continue to think that approach is philosophically valid. Again, it's a high-level problem that could be helped by myriad unrelated solutions.

But I'm still looking for a general proposal on how this process should be done. If we go to one solution per proposal, we'll see an explosion of proposals, many sharing enough attributes that they might all be addressed by one project-scale, high-level solution. We'd have a lot of proposals to stay on top of, and a lot more threads here (posts would likely be equal).

If we allow any multiple solutions per proposal at all, we're going to get the sort of situation we have now. It's no accidental coincidence that the problem you're citing, Quim, is common to the most popular proposals. There's a competition amongst solution creators. Collaboration could solve the problem but how do we help that happen?

So... how do we design our way out of this? And am I correct in assuming the instructions I originally created for the How To are totally wrong?