Consumer Rights Wiki talk:AI usage policy

Consumer Rights Wiki contributor JamesTDG proposed on 20 September 2026 that the wiki's AI usage policy add a "signal flare" requirement obliging anyone running LLM-powered automation to test as many edge cases as possible before letting the automation run, citing recent incidents of bot edits producing errors that were difficult to patch manually. In the same talk-page thread, user Capitain Jack suggested renaming the policy's "common signs of AI writing" section to "common signs of careless writing," arguing the listed habits — over-bolding, fluffy comparatives, indicator words and URL-less parenthetical sources — are careless-writing markers rather than proof of AI authorship.

"Signal flare" requirement: new section | ← Older revision | | Revision as of 18:08, 20 September 2026 | | | Line 34: | | Line 34: | | | | :So one small suggestion, and it is a naming change rather than a policy change. The section titled "common signs of AI writing" is accurate about what it lists, and I use it as a checklist against my own drafts, but every item on it describes careless writing rather than a particular author. Over-bolding, fluffy comparatives, indicator words and sources given in parentheses without a URL were all human habits first, and they are still mostly human in practice. Read as "common signs of careless writing" the same list catches strictly more, it stops being a claim about who wrote something, and it no longer needs the caveat about edge cases, because nobody is insulted by being asked to write carefully. | | :So one small suggestion, and it is a naming change rather than a policy change. The section titled "common signs of AI writing" is accurate about what it lists, and I use it as a checklist against my own drafts, but every item on it describes careless writing rather than a particular author. Over-bolding, fluffy comparatives, indicator words and sources given in parentheses without a URL were all human habits first, and they are still mostly human in practice. Read as "common signs of careless writing" the same list catches strictly more, it stops being a claim about who wrote something, and it no longer needs the caveat about edge cases, because nobody is insulted by being asked to write carefully. | | | :Everything else in the policy already does the work. The checklist tests the artefact, and an artefact is either checkable or it is not. User:Capitain jack\|Capitain Jack User talk:Capitain jack\|talk 15:30, 20 September 2026 UTC | | :Everything else in the policy already does the work. The checklist tests the artefact, and an artefact is either checkable or it is not. User:Capitain jack\|Capitain Jack User talk:Capitain jack\|talk 15:30, 20 September 2026 UTC | | | | | == "Signal flare" requirement == | | | | | So lately we have been experiencing some users using LLM powered agents to handle automating tasks on the wiki. While the work that they are doing is great and all, we severely need to append the policy for LLM-powered automation, so that we don't have to deal with a large block of edits being made with errors that are difficult to manually patch. | | | | | Simply put, set up a requirement for any sort of automations to send off a signal flare with as many edge cases tested as possible before being left to run. | | | | | I do believe we could use a better phrasing for the rule, though. User:JamesTDG\|JamesTDG User talk:JamesTDG\|talk 18:08, 20 September 2026 UTC |