The archive provides Chinese and English research texts. Translations may be AI-assisted and may not yet have received independent human review. Consult the original-language sources alongside them.
Research is ongoing; collected events do not constitute a complete case history.
View full image ↗Opening page of the source document associated with “AI, but fair: creative-industries position paper on AI use”. Original page layout retained; follow the source for the full text.
Image source: Illustratoren Organisation e.V.; rights remain with the original rights holders.
Source · AI, but fair: creative-industries position paper on AI use ↗The start date is only the earliest event collected in this batch; it does not assert that the controversy began that day.
Case chronology
IO publishes joint creative-industries position, KI aber fair
IO published a joint position demanding creators’ authorisation and remuneration, training-data transparency, and AI-output labels, arguing that repeated individual refusals were impractical while remaining open to technological progress.
AGD explains why it did not sign KI aber fair
AGD said it did not sign because the text’s problem framing and policy demands were too general. It advocated discussion of designers’ opportunities, risks, and professional training in AI use, and also expressed interest in disclosure of training materials.
Research question
Preserves differences within a profession over training permission, remuneration, and technological adaptation, without merging all creators’ organisations into one anti-AI camp.
Related documents
DOC-0193AI, but fair: creative-industries position paper on AI useDOC-0194Our position on AI, but fairDOC-0466IO members’ meeting 2025DOC-0593#noAI — Do we need a quality label?DOC-0969IO2023 general assembly reportSources
Illustratoren Organisation e.V. · DE · 2023-04-04
Related cases
Cite this record
ANTI-AI ARCHIVE. “KI aber fair / German creative associations’ licensing demands and AGD’s refusal to sign.” case-0124. Include this page’s URL and your access date when citing.

