The rules are written; they're just not all in that one document. The balance HN strikes here is something Dan has worked out over a very long time. There's at least two problems with arbitrarily fleshing out the guidelines ("promoting" "case law" to "statutes", as it were):
* First, the guidelines get too large, and then nobody reads them all, which makes the guideline document less useful. Better to keep the guidelines page reduced down to a core of things, especially if those things can be extrapolated to most of the rest of the rules you care about (or most of them plus a bunch of stuff that doesn't come up often enough to need space on that page).
* Second, whatever you write in the guidelines, people will incline to lawyer and bicker about. Writing a guideline implies, at least for some people, that every word is carefully considered and that there's something final about the specific word choices in the guidelines. "Technically correct is the best kind of correct" for a lot of nerds like us.
Perhaps "generated comments" is trending towards a point where it earns a spot in the official guidelines. It sure comes up a lot. The flip side though is that we leave a lot of "enforcement" of the guidelines up to the community, and we have a pretty big problem with commenters randomly accusing people of LLM-authoring things, even when they're clearly (because spelling errors and whatnot) human-authored.
Anyways: like I said, this is pretty well-settled process on HN. I used to spend a lot of time pushing Dan to add things to the guidelines; ultimately, I think the approach they've landed on is better than the one you (and, once, I) favored.