"This proposal is vague in its usefulness" is the same thing as not adhering to specific, written, agreed upon goals and principles. So you could say "yes if th

"This proposal is vague in its usefulness" is the same thing as not adhering to specific, written, agreed upon goals and principles. So you could say "yes if this becomes more specific in relation to X". However, this situation can also easily arise where the goals and principles are vague, and in that case it's ultimately means that its more of a vague reasons to say no than a vague proposal. The "it's potentially extra work and extra code to manage" is, imo, another wildcard vague reason to say no. It can be used to deny essentially any proposal anybody makes. It's Machiavellian. In a cooperative teamwork oriented environment, those things are given budgets so there can be some wiggle room for each proposal to progress.