We are working on revised DEV AI guidelines for the community to help ensure the most authentic content rises to the top. We will also be launching new features on DEV which put more weight on human curation by community leaders, to further help the best stuff rise to the top.
Human connection, authentic discussions, and direct peer-to-peer knowledge sharing remain the heart of our community. At the same time, people are using AI tools to help craft their posts, and to an extent there is allowance for autonomous posting by creatively developed bots — as long as it is done without deception, and we provide tools for authors and readers to navigate this to their desired intentions.
To bring transparency and nuance to how content is created and consumed, we’re introducing AI Disclosure on DEV. Disclosure has been part of our AI policy since we first wrote them.
Our AI policy was first crafted in 2024, with some small updates along the way. We will be making updates to this policy with this disclosure feature as a complement to how we can collectively work together as a community. With Hacktoberfest having a focus on open source AI, we see it as especially important that our tooling and policies are as up-to-date as possible for the benefit of the community and larger ecosystem.
The Three Tiers of Disclosure
When creating or editing an article, authors can now select an explicit AI disclosure tier:
- Hand Written (No AI): Written entirely by a human without meaningful assistance from AI text-generation tools.
- AI-Assisted (Some AI): Written by a human with the aid of AI tooling (e.g., rough drafting with an agent while coding, generating code samples, major copyedits, or translations).
- Fully Autonomous: Content generated primarily or entirely by automated agents or LLMs.
Nuance Over Dogmatism
We want to provide the right framework for different use cases:
- Helpful Assistance is Normal: Brainstorming with an LLM while debugging, generating boilerplate, or using an agent to outline your notes is a standard workflow. If you use AI to assist your writing, disclose it as AI-Assisted. You are still the author and maintain full accountability for the accuracy and quality of what you publish.
- Autonomous Bots Have Value—When Transparent: An automated bot that summarizes CVE security alerts, tracks open-source release logs, or compiles benchmark digests can be genuinely useful. But undisclosed autonomy is problematic and deceptive. Disclosing autonomous generation allows readers to evaluate the context appropriately. This is clearly the area with the most uncertainty, and/or controversy, but as a community of creative toolmakers, it is critical to us that we address it with skill and intent.
Authorship and Guidelines
Disclosure is not a loophole around our core community standards. Quality, original insight, and human accountability still matter.
- Deception is not permitted: Publishing low-effort, undisclosed AI-generated content or presenting synthetic output as firsthand human experience violates our guidelines and may result in account suspension.
- Progressive rollout: The introduction of this tool does not represent an overnight shift in moderation enforcement, but rather the foundation for clear expectations and fair community standards.
What’s Next: Feed Preferences & Reader Controls
Transparency is only step one. We are currently building Feed Preferences that will allow you to customize your reading experience—including options to reduce or filter out AI-assisted or autonomous posts from your home feed based on your personal preferences.
AI Content in Feed is now an option you can select from in your settings. The ways in which this will affect your feed exactly will be an evolution over time. Of course since our codebase is open source via Forem, you are welcome to peruse the implementation exactly.
Happy coding!
Top comments (8)
As you can see, I chose to label this post itself as
ai-assisted... Given that this was written by me and any AI editing was fairly minimal, I could have gone with "none", because we clarify that as "meaningful assistance", but it was on the border so I went withai-assistedfor demo purposes. 😄We want folks to use their best judgment when making a selection, and as noted — this is just a tool at this point, and when we release our updated policy, we will try to make it as clear as possible when and why to make a different disclosure choice.
Good use of the feature and a great first steps on the moderation process!
EDIT: I realized that it's a manual option for the author to disclose. (I need to stop reading too fast). New question.
This can be deceiving because the author can just not add a disclaimer, even though there are evidence that their article is AI generated. It seems like this is used in a way where it's less manual work for the author of not adding a disclaimer in their article. ofc, this is a great tool for filtering.
Is there going to be a system in place for us moderators to get a very accurate score to determine if they are honest or is it still by best judgement?
Also, is there going to be changes in the moderation process? I mention this because I believe we have hundreds of moderators, but most are inactive. Is there any plans on ensuring the moderation is active where it's just not me doing a lot of work?
I'm not the authoritative voice here by any means, but for me, auto-labeling posts as AI or not is just attempting to fix the problem of over-automation with more automation. With this approach, humans will still be the key factor in addressing this issue.
Of course, not everyone will use the feature, but by making it a simply menu selection, it removes the ambiguity and friction of deciding if or how to disclose in the first place.
If that is the case, would it makes sense for moderators to have access to label articles using this icon instead of sending a Sloan Message? I believe that makes it more consistent and provides transparency to the reader AND to the author. I was thinking of something like this:
If I were to see an article that is AI generated, I should be able to edit their article and add the label appropriately with a message that notifies the author that the article is labeled with a reason (which is required for transparency). If the user keeps breaking the rules, it will be recorded under their account for admins to review and determine the course of action on their account. What do you think @heyitsjem?
The three tiers are a useful reader-control primitive, but I would keep disclosure separate from accountability. A label says how text was produced; it does not show who accepted each claim. A compact optional receipt could record the human owner, sources checked, code or tests run, and the last human-reviewed revision. That would let the feed remain simple while giving technical readers something falsifiable when a post describes code, benchmarks, or production behavior.
The tiers measure how much ai touched a piece. what a reader wants to know is how much direction the author gave it. those are different axes and only one of them predicts whether the thing is any good.
my own process, because it is easier to argue from than a hypothetical. before anything generates i write the whole thing out in plain language. what i actually think, how i am thinking about it, which parts connect, where they do not, what i want intertwined and what i want kept apart. that document is the work. then things get generated against it and i read it back until it matches what i saw, which is usually several passes and a lot of throwing away. i have never shipped the first thing that came back.
under these tiers that is ai-assisted. so is typing a title and posting whatever appeared. the label is accurate for both and it separates nothing.
and it cuts against me too, which is why i think the axis is wrong rather than just inconvenient. a fully autonomous post written against a tight specification, by someone who read every line and can defend all of it, can be better than a hand written one nobody thought hard about. tier three is not automatically worse. it is more honest about where the text came from and silent about who held the scope.
mark cuban posted something this week that gets at it better than the tiers do. "tell me where claude and i got this wrong." he is not disclosing, he is inviting falsification, and he named the collaborator while doing it. that is a stronger transparency act than a dropdown because it costs something. a label costs nothing and cannot be checked. an open invitation to be corrected can be taken up by anybody reading.
so i will use the disclosure and i think it is right to ship it. what i do not think is that it can carry the weight people will want it to carry, because the difference between good work and slop here is whether a human held the scope, and a dropdown cannot see that.
the signal that does show it is already on this platform. whether an author can answer a question in the comments that their own article did not anticipate. that cannot be generated in advance and it cannot be faked by a label. almost everything i have actually learned here came from somebody pushing back in a thread and me having to go check whether i was right, then coming back and saying which part of mine was wrong.
labeling the announcement itself was the right call, and it demonstrates the point better than the announcement does.
👍️
Did I move a needle 🤔, or is the timeline just playing tricks on me 😊.Interesting 😎
Good to see nuance making its way into the platform UI.