clowdr.devAcceptance 01
Taste stays human
Generated output is raw material until someone with taste selects, edits, rejects, or rebuilds it.
How We Ship
AI is not the line. Shipping is.
We do not sort contributors by tool purity. We care about taste, accountability, polish, rights, and whether the final game is worth playing.
The standard
Tools do not ship games. Contributors do.
Professional game development has always been craft under constraints. Tools can speed up production, but they do not replace judgment. A Clowdr contributor owns the output they submit: the code they test, the asset they polish, the audio they shape, the mechanic they choose, and the handoff they agree to.
Read the operational AI StandardThe filter
This will not be for everyone.
If you believe any AI use is morally disqualifying in game development, Clowdr probably is not for you. We respect that position. We do not share it, and we are not going to litigate it here.
What we mean
The work has to hold up.
Acceptance 02
Quality beats purity
The question is not whether a tool was involved. The question is whether the result is coherent, playable, performant, and credited fairly.
Acceptance 03
Accountability is not optional
If you use a tool, you still own the result. Tested code, optimized assets, clean handoffs, and clear rights are part of the work.
Across the team
Every craft keeps its standards.
Artists
AI can help explore mood and variation, but style, polish, cohesion, optimization, and rights still belong to the artist.
Read the artist standardComposers
AI can help with references and temp direction, but emotion, timing, mix, implementation, and identity still belong to the composer.
Read the audio standardDevelopers
AI can help write code, but architecture, testing, maintainability, and product judgment still belong to the developer.
Read the developer standardUse the tools. Own the result. Ship the game.
Clowdr is for contributors who want structure, standards, and shipped credits. Not tool worship. Not tool panic. Finished work.