Question for free/open-source game jams and project communities.
If a FOSS game project, jam, or community showcase allows written material such as design notes, devlogs, lore, tutorials, or README updates, how would you handle AI-detector scores in moderation?
The problem I see is that a detector report can look like evidence, but it is still probabilistic. In a small free-game community, a false accusation could damage trust, while ignoring obvious low-effort generated submissions can also hurt the project.
The boundary I would use:
- do not treat a detector score as proof of authorship or misconduct
- expect false positives and false negatives
- ask for source context such as commit history, drafts, screenshots, or design rationale
- avoid public accusations in project threads
- do not upload someone else's private drafts or school/work files into a detector without permission
- keep any review process focused on project quality, license clarity, and contributor norms
- let maintainers make a manual judgment rather than outsourcing the decision to a percentage
For free game projects, would you put this in jam rules, contribution guidelines, moderator notes, or project showcase expectations?
No product link is needed. I am asking about FOSS game community moderation and contributor trust, not recommending a detector.