You're right that the article has some marginal value. I think many deletionists would even agree.
The problem is risk/reward. Every WP article is a commitment to defend a topic against entropy and malice. Every article is part of the attack surface exposed to vandals and spammers.
So in the view of most of Wikipedia, articles that are fated to forever remain "stubs" have negative net value.
Reasonable people can obviously disagree about this, but I find the deletionist argument against zombie stub articles to be very compelling.
But at this point you've basically given up any attempt of civil community processes and you're doing things not because they are right, but because not doing them might give the enemy a speculative advantage.
But that's very much not the case with other stub articles, or even other zombie articles (where sources have no doubt been permanently exhausted, but the sources we have today make room for a solid 100 word article).
All over some moderately important issue, at best.
You only need to lock stub articles that repeatedly have people add unverifiable info to them.
Finally, if the pages doesn't exist, then anyone who wants to exercise the "option...to quickly add coverage" doesn't have access to the info that would have been contained in the stub!
I can't understand why you think one can't defend against this stuff using mechanism that don't lead to effects like the one described by rsync https://news.ycombinator.com/item?id=13159057
>rsync.net has been mentioned in the press widely over the course of over 10 years - everything from articles about our warrant canary to articles about our ZFS support. In fact, other wikipedia pages mention and discuss rsync.net.
So it's had some coverage related to first commercial use of a warrant canary and is discussed in that context. It commercially implemented a feature of rsync (the application) that should be talked about on the page about rsync the application. But what can be said about rsync.net? Maybe someone read about their warrant canary and wants to know more about this company...but no independent source has written about who they are and what makes them so savvy with opsec and rsync. Anything outside those narrow topics is original research or primary sources. I think things are working as intended.
https://news.ycombinator.com/item?id=13161015
(better if replies go there too)
The fact that the band exists and has a newspaper article about it is helpful. Otherwise it's article will be very short. So what?
> All of this applies equally well to little-known authors, random Indian corporations, and your cat.
Yes to the first two. (My cat has zero verifiable information about it.) They will have very tiny stub articles. So what?
> If all we have to go on is a couple of primary sources and maybe a passing mention in the press, what is there to say without giving undeserved credence to the primary sources?
So don't say anything else.
I really, really don't understand what's motivating your position. I'm trying!
> But really, I'm just rewriting the ideas of the consensus based notability guideline, which is much better written and specific: https://en.wikipedia.org/wiki/Wikipedia:Notability
That page is almost exclusively about defining notability (which, because of the intrinsic vagueness, necessarily takes a long time and is mostly unsuccessful). The only part that's directly about the reasons for the requirement is this subsection:
https://en.wikipedia.org/wiki/Wikipedia:Notability#Why_we_ha...
And the only argument it brings up that I didn't address is this: "We require multiple sources so that we can write a reasonably balanced article that complies with Wikipedia:Neutral point of view, rather than representing only one author's point of view." This, again, is something that can easily be addressed by just requiring verifiability to include coverage by multiple sources. (Even in highly notable articles, there are a large number of facts that are only verified through a single source; this isn't a reason to delete the fact.)