I'd be a wee bit cautious with the "AI edited" part of it; since that might exclude a number of people with disabilities or for whom english is a second (or third, or later) language.
My reading is that the intent is to have a human voice behind the text.
Monitor and see how it goes I guess!
As a not native speaker, for me using something like Google Translate is fine, it's literal enough to keep the author voice. [1]
Also writing a draft in Google Docs and accepting most [2] of the corrections is fine. The browser fix the orthography, but I 30% of the time forget to add the s to the verbs. For preposition, I roll a D20 and hope the best.
I'm not sure if these are expert systems, LLM, or pingeonware.
But I don't like when someone use a a LLM to rewrite the draft to make it more professional. It kills the personality of the author and may hallucinate details. It's also difficult to know how much of the post is written was the author and how much autocompleted by the AI:
[1] Remember to check that the technical terms are correctly translated. It used to be bad, but it's quite good now.
[2] most, not all. Sometimes the corrections are wrong.
Yes even I posted something recently which was voted down since I mentioned from get go that I used help from AI. But the idea was mine, I wrote the first draft, and then worked with AI in 2-3 loops to get it right.
But like dang said ... I do not have time to fight this battle when I have only 10 minutes :)
I need to say something about this but it might have to be later as I have to run out the door shortly...
The short version is that we included it to protect users who don't realize how much damage they're doing to their reception here when they think "I'll just run this through ChatGPT to fix my grammar and spelling". I've seen many cases of people getting flamed for this and I don't want more vulnerable users—e.g. people worried about their English—to get punished for trying to improve their contributions. Certainly that would apply to disabled users as well, though for different reasons.
Here are some past cases of these interactions: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu....
Edit: uni_baconcat makes the point beautifully: https://news.ycombinator.com/item?id=47346032.
Most rules in https://news.ycombinator.com/newsguidelines.html have a lot of grey area, and how we apply them always involves judgment calls. The ones we explicitly list there are mostly so we have a basis for explaining to people the intended use of the site. HN has always been a spirit-of-the-law place, and—contrary to the "technically correct is the best correct" mentality that many of us share—we consciously resist the temptation to make them precise.
In other words yes, that bit needs to be applied cautiously and with care, and in this way it's similar to the other rules. Trying to get that caution and care right is something we work at every day.