<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>[DISCUSSION] AI Rules Overhaul</title>
		<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul</link>
		<description>Posts in the discussion thread &quot;[DISCUSSION] AI Rules Overhaul&quot; - Clarifications, removal of the warning revocation, and possibly disallowing AI translations</description>
				<copyright></copyright>
		<lastBuildDate>Tue, 13 Oct 2026 01:22:31 +0000</lastBuildDate>
		
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7201457</guid>
				<title>Re: [DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7201457</link>
				<description></description>
				<pubDate>Thu, 18 Sep 2025 21:42:28 +0000</pubDate>
				<wikidot:authorName>Kufat</wikidot:authorName>				<wikidot:authorUserId>2336666</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>I think one of the ways to go about it could be to look for signs of something being an AI translation (assuming AI translations have similar hallmarks to regular AI texts) and just deciding based on that. If somebody uses AI just for help in translation, those hallmarks shouldn't really be there at all.</p> </blockquote> <p>This doesn't really answer the question that I asked, which was how to write an enforceable rule that would meet your criteria. I can't think of a good wording and was hoping that you might have one in mind.</p> <blockquote> <p>Regarding the good faith exception, I think I would just cut out the &quot;The image is cited properly when used on the Wiki and appears to be compliant with both our license and the Image Use Policy.&quot;</p> </blockquote> <p>I don't think we should grant an exception to the AI rules in cases where a user is breaking other rules at the same time.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7200514</guid>
				<title>Re: [DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7200514</link>
				<description></description>
				<pubDate>Wed, 17 Sep 2025 10:28:45 +0000</pubDate>
				<wikidot:authorName>Ethagon</wikidot:authorName>				<wikidot:authorUserId>5844683</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I think one of the ways to go about it could be to look for signs of something being an AI translation (assuming AI translations have similar hallmarks to regular AI texts) and just deciding based on that. If somebody uses AI just for help in translation, those hallmarks shouldn't really be there at all.</p> <p>In essence, I think our current methods are only really good at detecting a fully AI-generated text, though I could be wrong here, so they can still be used to determine if something is over the line or not.</p> <p>Regarding the good faith exception, I think I would just cut out the &quot;The image is cited properly when used on the Wiki and appears to be compliant with both our license and the Image Use Policy.&quot; That's already handled by the Image Use policy itself and the first point gets at the essence of it better.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7198971</guid>
				<title>Re: [DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7198971</link>
				<description></description>
				<pubDate>Mon, 15 Sep 2025 00:31:11 +0000</pubDate>
				<wikidot:authorName>radian628</wikidot:authorName>				<wikidot:authorUserId>9301014</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>Would changing &quot;The image is not described as having been generated by AI, and the poster has no knowledge that it was AI-generated.&quot; to something like &quot;The poster has no knowledge that it was AI-generated after having done a reasonable amount of diligence.&quot; address your concern here?</p> </blockquote> <p>Yep, something like that sounds good to me.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7198900</guid>
				<title>Re: [DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7198900</link>
				<description></description>
				<pubDate>Sun, 14 Sep 2025 21:34:33 +0000</pubDate>
				<wikidot:authorName>Kufat</wikidot:authorName>				<wikidot:authorUserId>2336666</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Do you have any suggestions for how it might be possible to write <em>and enforce</em> a rule that allows some use of AI translation without allowing a full AI translation?</p> <p>Re. the good faith exception, it's not a punishment for misattribution. It's a limited <em>exemption</em> from punishment for breaking the AI rule. I'm open to suggested changes in wording if you have any.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7198895</guid>
				<title>Re: [DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7198895</link>
				<description></description>
				<pubDate>Sun, 14 Sep 2025 21:27:05 +0000</pubDate>
				<wikidot:authorName>Kufat</wikidot:authorName>				<wikidot:authorUserId>2336666</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>That said, I don't know what percentage of people would actually go through the trouble of appealing, nor am I part of Disc/AHT, so I'm not totally sure if this is an actual problem.</p> </blockquote> <p>It's a reasonable thing to consider, but based on the quantity of AI ban appeals we receive I wouldn't expect it to be a problem even if they increased by a substantial percentage.</p> <blockquote> <p>I do think users should be expected to look for such disclaimers. I also wonder if such a misunderstanding would be something that could just be explained in a user's ban appeal.</p> </blockquote> <p>It's something we'd consider as part of an appeal, yeah. I'll note that nobody has yet tried to make use of the good faith exception, nor have there been any cases where staff has found that it's applied to a given situation.</p> <p>Would changing &quot;The image is not described as having been generated by AI, and the poster has no knowledge that it was AI-generated.&quot; to something like &quot;The poster has no knowledge that it was AI-generated after having done a reasonable amount of diligence.&quot; address your concern here?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7198338</guid>
				<title>Re: [DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7198338</link>
				<description></description>
				<pubDate>Sun, 14 Sep 2025 12:28:28 +0000</pubDate>
				<wikidot:authorName>Ethagon</wikidot:authorName>				<wikidot:authorUserId>5844683</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Regarding AI translations:</p> <p>I'm fully opposed to a full ban of tools like DeepL translator. I'm a bit biased here since I also sometimes use Google translate if I'm not pleased with a sentence in English, use translate to make it german (my mother language), change it a bit so I think it fits better and then translate it back to english.</p> <p>I think valid usecases also come up regularly for translations. If I forget the good translation for a single word I can look it up in a dictionary. When that extends to more complex sentence structures or idioms, machine translators are often the better tool to help you. (And in the end it's up to the translator familiar enough with both languages if this is a good phrase to use or not).</p> <p>I think usage of tools like DeepL translator in this or a similar manner has no effect on how creative of a medium translation (or regular writing, which, as I said, can also be affected here for people whose mother language isn't English) is and don't think of it as making it more mechanical than by using tools like a dictionary.</p> <p>None of this applies for complete machine translations. Full AI translations are something that I don't think are a good thing to have on the wiki. I think the best place would be for the Translation Policy to be amended to disallow complete machine translations, but leave leeway for normal usage of allowed translator tools.</p> <ul> <li>Removal of Warning Revocation: This makes sense to me, given the revoke seems to be either ignored or the account abandoned</li> <li>Including the Sandbox: I've been slightly opposed to this in the past, because stuff like AI-generated ideas are allowed, so I think storing them on the sandbox. I don't think this is a thing that comes up in practice, so I think this is a good idea.</li> <li>deletions rule: support</li> <li>good faith exception: I'm unsure how Licensing currently handles attribution mistakes, but this reads to me that not fulfilling all three exceptions means you get a permaban. The second point for example should only be punished to the extent that normal misattribution would be. The third point makes sense. There's no excuse if you made an AI-generated image.</li> <li>support for the rest</li> </ul> <p>If not Grammarly, then at least one spellchecker software should be added back on the allowed list, so it's clear that regular spellchecking is on the okay list (though I do think calling out the case of Grammarly specifically might be worthwhile, since we have strict line we draw there on what parts of Grammarly are allowed and what aren't, I believe)</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7197229</guid>
				<title>Re: [DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7197229</link>
				<description></description>
				<pubDate>Sat, 13 Sep 2025 22:37:15 +0000</pubDate>
				<wikidot:authorName>radian628</wikidot:authorName>				<wikidot:authorUserId>9301014</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Overall, here's my thoughts on the AI Policy Rework:</p> <p>In short:</p> <ul> <li>Banning AI Translations: Full Support</li> <li>Removing Initial Revoke: Almost Full Support; concerned about quantity of permaban appeals.</li> <li>Narrowing Good-Faith Exception: Almost Full Support; concerned about good-faith users forgetting to check AI disclaimers on image sites.</li> </ul> <p>In long:<br /> Banning AI Translations: Full support of banning machine-generated translations. It's an art form unto itself and machine-generated translations are disrespectful to the original author as they often do not properly capture their artistic intent.</p> <p>Removing the Initial Revoke: Almost full support here. I feel like if someone's decided to use AI in the first place, they've either (1) not read the rules, indicating a lack of maturity, or (2) have a mindset surrounding creative work incompatible with that of the wiki which will likely lead to more clashes in the future. A revoke is just a bandaid to either of these problems because they go deeper than just a misunderstanding. That said, I do worry that people banned for AI will immediately appeal, creating work for staff in the long run as they have to process the flood of appeals, so it might be worth adding some sort of provision to filter out or delay or otherwise expedite them. That said, I don't know what percentage of people would actually go through the trouble of appealing, nor am I part of Disc/AHT, so I'm not totally sure if this is an actual problem.</p> <p>Narrowing the Good-Faith Exception: This one I'm largely in support of, but I do feel like it's worth showing a bit more leniency here than the rules would imply as-written, specifically for cases where someone might've simply forgotten to explicitly check the page for &quot;this was made by AI&quot; disclaimers. I think that's a reasonable mistake to make, especially when the disclaimers on some of these websites might not be in an immediately obvious place, or when one might not have developed the &quot;muscle memory&quot; to consciously look for them while searching for images, because it's easy for one to tunnel-vision and forget these things while in the thick of sifting through tens or hundreds of images for the perfect one for an article. All that said, in the long run, I do think users should be expected to look for such disclaimers. I also wonder if such a misunderstanding would be something that could just be explained in a user's ban appeal. Overall, despite this concern, I'm in support of this change.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://05command.wikidot.com/forum/t-17247412#post-7197178</guid>
				<title>[DISCUSSION] AI Rules Overhaul</title>
				<link>https://05command.wikidot.com/forum/t-17247412/discussion-ai-rules-overhaul#post-7197178</link>
				<description></description>
				<pubDate>Sat, 13 Sep 2025 21:25:09 +0000</pubDate>
				<wikidot:authorName>Kufat</wikidot:authorName>				<wikidot:authorUserId>2336666</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>04 mirror: <a href="https://scp-wiki.wikidot.com/forum/t-17247411/discussion-ai-rules-overhaul">https://scp-wiki.wikidot.com/forum/t-17247411/discussion-ai-rules-overhaul</a></p> <h2><span>Rules text</span></h2> <h3><span>Current rule</span></h3> <div class="collapsible-block"> <div class="collapsible-block-folded"><a class="collapsible-block-link" href="javascript:;">+&nbsp;show&nbsp;block</a></div> <div class="collapsible-block-unfolded" style="display:none"> <div class="collapsible-block-unfolded-link"><a class="collapsible-block-link" href="javascript:;">–&nbsp;hide&nbsp;block</a></div> <div class="collapsible-block-content"> <blockquote> <ol> <li><strong>AI-generated content</strong> <ol> <li>The use of generative<sup class="footnoteref"><a id="footnoteref-881488-1" href="javascript:;" class="footnoteref" >1</a></sup> machine learning<sup class="footnoteref"><a id="footnoteref-881488-2" href="javascript:;" class="footnoteref" >2</a></sup> models to generate user facing content<sup class="footnoteref"><a id="footnoteref-881488-3" href="javascript:;" class="footnoteref" >3</a></sup> is banned. <ul> <li>Users who post AI-generated content to the SCP wiki will receive a revocation of membership on their first offense, and a permanent ban on the second.</li> <li>Good faith exception: This policy does not apply to properly-cited images from external sources unless they were created by, for, or at the behest of the user who posted them to the Wiki.</li> </ul> </li> <li>Furthermore, the usage of tools whose primary use is generative machine learning is also banned for user facing content.</li> <li>All exceptions to this policy are on the following white list: <ol> <li>(This list is currently empty)</li> </ol> </li> <li>Examples of banned content include but are not limited to <ol> <li>ChatGPT-generated text</li> <li>Midjourney/Stable diffusion</li> <li>AI voice generation</li> </ol> </li> <li>Examples of allowed content <ol> <li>DeepL translator, Grammarly (proofreading/spellcheck assistance only. No AI-generated content or AI-revised/rewritten material)</li> <li>Fractal generation</li> <li>Traditional text to speech (if license compatible)</li> <li>AI-generated CSS code</li> <li>Writing stories about AIs</li> </ol> </li> </ol> </li> </ol> </blockquote> </div> </div> </div> <h3><span>Proposed Rule</span></h3> <blockquote> <ol> <li><strong>AI-generated content</strong> <ol> <li>The use of generative<sup class="footnoteref"><a id="footnoteref-881488-4" href="javascript:;" class="footnoteref" >4</a></sup> machine learning<sup class="footnoteref"><a id="footnoteref-881488-5" href="javascript:;" class="footnoteref" >5</a></sup> models to generate, <span style="text-decoration: underline;">translate</span>, or edit user facing content<sup class="footnoteref"><a id="footnoteref-881488-6" href="javascript:;" class="footnoteref" >6</a></sup> is banned. <ul> <li>Posting generative machine learning (AI-generated) content to the SCP Foundation Wiki, the associated forums, or any official Sandbox in violation of this rule will result in a permanent ban. This ban may be appealed through the standard disciplinary process.</li> <li>Good faith exception for images: Users will not be banned for making use of AI-generated images from external sources provided all of the following conditions are met for a given image: <ul> <li>The poster has no knowledge that it was AI-generated after having done a reasonable amount of diligence.</li> <li>The image is cited properly when used on the Wiki and appears to be compliant with both our license and the <a class="newpage" href="https://05command.wikidot.com/image-use-policy">Image Use Policy</a>.</li> <li>The image was not created by, for, or at the behest of the user who posted it to the Wiki.</li> </ul> </li> </ul> </li> <li>All pages containing AI-generated text will be eligible for summary deletion under the standard summary deletion procedure. <ul> <li>All AI-generated images and other media will be removed by staff, irrespective of whether the good faith exception applies.</li> </ul> </li> <li>Furthermore, the usage of tools whose primary use is generative machine learning is also banned for user facing content.</li> <li>Examples of banned content include but are not limited to <ol> <li>Any ChatGPT-generated text or images, including modifications of existing text or images</li> <li><span style="text-decoration: underline;">DeepL translator</span></li> <li>Midjourney/Stable diffusion</li> <li>AI voice generation</li> <li>Almost any system which generates text or media in response to a free-text prompt</li> </ol> </li> <li>Examples of allowed content <ol> <li>Fractal generation</li> <li>Traditional text to speech (if license compatible)</li> <li>AI-generated CSS code</li> </ol> </li> </ol> </li> </ol> </blockquote> <h2><span>Rationale</span></h2> <h3><span>Removal of warning revocation</span></h3> <p>By this point, just about everyone with access to the Internet is aware that the use of generative AI is widely disallowed. Between that and the multiple mentions in our rules and Join the Site page, we make it clear that this applies to the Wiki as well. In addition, staff has noticed that almost nobody who has received a revocation for AI usage has gone on to produce a successful article legitimately. (They generally either use AI again and get banned or else abandon their accounts.)</p> <p>In essence, the purpose of revoking on the first use of AI was to encourage users to instead contribute legitimately. This hasn't worked out in practice. Removing the warning revocation <em>may</em> help discourage AI use and <em>will</em> help reduce the likelihood of staff having to spend time dealing with the same user twice.</p> <h3><span>Including the Sandbox</span></h3> <p>All mainsite rules already apply to the Sandbox. This is technically redundant but serves as a potentially-useful reminder.</p> <h3><span>Deletions rule</span></h3> <p>This rule makes it explicit that AI-generated pages may be summarily deleted. This won't change the existing practice, but it'll help make it clearer to users and staff alike.</p> <h3><span>Modifications to good-faith exception</span></h3> <p>This exception is designed to be narrow. It was written to ensure that people who put in the work required to find and properly cite images compatible with our license and rules don't get banned for failing to realize that those images are AI-generated. The changes increase the clarity of the rule for staff and users.</p> <h3><span>Translations</span></h3> <p>Translation of fiction is an inherently creative endeavor. By allowing the use of AI for translation but not composition, we imply that translation is mechanical work on par with generating CSS to meet specifications. I don't believe this to be the case. Translations have their own <a href="https://literarytranslators.org/awards/">awards</a> and we've long recognized the work of translators by crediting them alongside authors in the attribution metadata. This puts translation in the same level as writing, as opposed to how we treat e.g. CSS.</p> <p>It's also worth noting that anyone who wants to view an -EN page in another language, or another language branch's page in English, is free to run it through a translator for their personal use. As popular browsers such as Chrome, Safari, and Firefox now have this functionality built-in I don't believe that the additional effort required on the reader's part will be significant.</p> <p>In addition, the subject of using AI for translation of portions of an article for in-universe purposes has been discussed. (E.g. an article on -EN, written primarily in English, with a section containing a poem written in French.) It's true that disallowing the use of AI for translations would make it more difficult for authors to include text in languages that they don't speak. However, this is already the case for other specialized domains of knowledge. We don't allow an author to make use of AI to transform dialogue into militarily-correct jargon or other vernacular, for example. Disallowing the use of AI for language translation would be consistent, and would also have the beneficial effect of encouraging cross-branch collaboration when an author's vision for a work required it.</p> <p>If adopted, this change would <strong>not</strong> be retroactive. Existing AI-translated works would remain on the site.</p> <h3><span>Removal of allowed list</span></h3> <p>The list was empty. If there's ever an exception that we allow, it'll be restored.</p> <h3><span>Removal of &quot;stories about AIs&quot; rule</span></h3> <p>This was redundant and only produced confusion. It seems better to only mention generation of content, not subject matter.</p> <h2><span>Discussion and Voting Procedure</span></h2> <p>There are two questions here:</p> <ol> <li>Should the overall rule change above be implemented?</li> <li>Should the use of AI for translations be disallowed? (I.e. should the underlined portions be included in the rule change?)</li> </ol> <p>I anticipate that the second question will be more controversial than the first. It seems reasonably likely that the first question may have consensus in the discussion stage without requiring a vote; on the other hand, I don't expect that to be the case for the second.</p> <p>If we need to vote on both questions, then the issue of whether AI translation will be allowed will be voted on as a separate question in the same vote. This will affect the underlined portions only. (If the overall modification passes but the vote results in AI translation being allowed, the underlined sections will be removed and 'DeepL translator' will return to the list of examples of <em>allowed</em> content.)</p> <p>If the overall modification passes without need for a vote but a vote is required for the translation question, then the new rule will go into effect with AI translations permitted in the interim. Should the voting results lead to translations being disallowed, that modification will go into effect following the conclusion of the vote.</p> <p>Edit log: incorporate suggestion based on radian628's input.</p> <p><iframe src="https://scpwiki.github.io/timer/timer.html?lang=en&amp;time=2025-09-20T21%3A26%3A32.356Z&amp;progress=Discussion+will+continue+for" align="" frameborder="" height="" scrolling="" width="" class="" style="width: 750px; height: 200px; border: 0; text-align: center;"></iframe></p> <div class="footnotes-footer"> <div class="title">Footnotes</div> <div class="footnote-footer" id="footnote-881488-1"><a href="javascript:;" >1</a>. The model produces more meaningful information than was input into the model.</div> <div class="footnote-footer" id="footnote-881488-2"><a href="javascript:;" >2</a>. An algorithmic system designed to replicate a given set of training data.</div> <div class="footnote-footer" id="footnote-881488-3"><a href="javascript:;" >3</a>. All content directly viewable to the user (e.g, text, images, audio, video, etc., excluding CSS, Javascript and other parts that communicate to the browser and not the user).</div> <div class="footnote-footer" id="footnote-881488-4"><a href="javascript:;" >4</a>. The model produces more meaningful information than was input into the model.</div> <div class="footnote-footer" id="footnote-881488-5"><a href="javascript:;" >5</a>. An algorithmic system designed to replicate a given set of training data.</div> <div class="footnote-footer" id="footnote-881488-6"><a href="javascript:;" >6</a>. All content directly viewable to the user (e.g, text, images, audio, video, etc., excluding CSS, Javascript and other parts that communicate to the browser and not the user). This includes both pre-generated content and content generated through interaction with a reader.</div> </div> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>