HN Debrief

Copyright does not protect AI-generated content in EU

  • AI
  • Regulation
  • Open Source
  • Programming
  • Media

The post points to a Munich local court decision holding that purely AI-generated material is not protected by copyright under EU law. The key distinction is not “AI involved” versus “no AI involved.” It is whether the system acted like a tool under meaningful human creative control, or whether the model itself supplied the expressive choices. Several people noted this is consistent with older copyright logic around automated recordings, generative systems, and the basic Berne Convention idea that copyright attaches to original human authorship.

If your business depends on owning or exclusively licensing AI-heavy outputs, start keeping evidence of human authorship now and assume pure model output may be effectively unprotectable. For open source and commercial software alike, separate human-written, AI-assisted, and machine-generated parts before a dispute forces you to reconstruct provenance.

Discussion mood

Mostly unsurprised and cautiously approving. People saw the ruling as consistent with existing human-authorship doctrine, but the mood turned anxious when the implications hit software licensing, provenance, and the fact that AI output can be unprotectable while still infringing someone else’s work.

Key insights

  1. 01

    Derivative works still stay locked up

    An AI-generated work can fail to earn its own copyright and still remain constrained by someone else’s underlying copyright. The translation example made this concrete. A machine translation of a public domain book is effectively free, but a machine translation of a copyrighted novel still depends on the original rights holder because the protected expression survives through the derivative work. This sharply limits the idea that unprotectable AI output automatically becomes safe to copy or distribute.

    Do not treat “no copyright in the output” as a clearance shortcut. Run AI-generated translations, rewrites, ports, and remasters through the same derivative-work review you would use for human-made adaptations.

      Attribution:
    • Lazare #1 #2
    • jefftk #1
    • freeone3000 #1
  2. 02

    Open source licenses may fail on AI-only code

    Copyright licenses only bite if there is copyright to enforce. Several comments pointed out that GPL, MIT, BSD, and Creative Commons can still cover the human-authored parts of a project, but they may be powerless over code or media that is purely machine generated. That reframes the risk. The issue is not that AI output makes a whole repository legally radioactive. It is that the enforceable boundary inside one project may become patchy and much harder to police.

    If you publish AI-assisted code, document which files or sections are human-authored and which are generated. Otherwise you may discover too late that your license only protects the wrapper and not the substance.

      Attribution:
    • pornel #1
    • randyrand #1
    • Ekaros #1
    • lg5689 #1
  3. 03

    Editing AI output may protect only the edits

    The practical reading of mixed-authorship cases is narrower than many product teams want. Touching up AI output does not automatically pull the whole work into copyright. If the human contribution is limited to color grading, cleanup, or a few modified lines, protection may attach only to those new expressive changes. The untouched machine-produced remainder may stay unowned. That makes “human in the loop” a weak defense unless the human actually remakes the result in a meaningful way.

    Do not rely on superficial review or cosmetic edits to turn generated output into owned IP. If exclusivity matters, make humans responsible for substantial rewriting, redesign, or recomposition and keep a record of that work.

      Attribution:
    • dijksterhuis #1
    • dgellow #1 #2
    • hmry #1
  4. 04

    Provenance will become a litigation tool

    Several comments converged on the same operational problem. Once ownership depends on proving human authorship, logs, drafts, prompts, editing history, and even model watermarks become evidence. That cuts both ways. A company may need records to defend its copyright, while an opponent may use watermarking or internal disclosures to attack the eligibility of a claimed work. The future fight is less about abstract theory and more about whether you can reconstruct how something was made.

    Treat authorship records as part of your build and publishing pipeline. Preserve version history, prompt logs, and edit trails now, because courts will not accept hand-wavy claims of human contribution later.

      Attribution:
    • EagnaIonat #1
    • somerandom2407 #1
    • hn_submit #1
    • m-s-y #1
  5. 05

    This follows existing authorship doctrine

    The strongest grounding comments argued that the ruling is not a sudden anti-AI turn. EU copyright already hinges on an author's own intellectual creation, and older edge cases around automated capture, generative music, and nonhuman creators point in the same direction. The novelty is not the legal principle. It is that modern AI pushes huge volumes of commercially important work into the old exception bucket. The lower-court status matters, but the doctrinal path is already visible.

    Plan around continuity, not reversal. Expect future cases to refine where the human-author line sits, not to bless fully autonomous generation as standard copyrightable output.

      Attribution:
    • kstenerud #1
    • mod50ack #1
    • chungusamongus #1
    • enquirewithin #1

Against the grain

  1. 01

    Tool-building is creative work too

    A few people pushed back on output-focused tests by pointing out that the real creative act may sit upstream in the system design. If someone builds a sophisticated agent pipeline, custom prompts, evaluators, or even a bespoke model, then reducing authorship to the final keystrokes or post-editing can miss where the human contribution actually lived. That critique does not defeat the ruling, but it exposes how poorly current doctrine maps to modern generative workflows.

    If your product depends on heavily engineered generation pipelines, watch for cases that distinguish authorship in the system from authorship in each output. You may need contracts and trade secrecy, not copyright alone, to protect that investment.

      Attribution:
    • jmward01 #1
    • thevinter #1
  2. 02

    AI output can increase liability instead

    Some comments rejected the idea that AI is a clean-room escape hatch for remakes, emulator work, or code ports. Even if the output itself is uncopyrightable, it can still copy protected expression closely enough to trigger infringement, or run into trademark and patent claims that this ruling does not touch. That flips the usual startup instinct. You may lose ownership without losing exposure.

    Do not use generative tools as a shortcut around clearance for ports, remasters, branded assets, or compatibility work. Have counsel review copyright, trademark, and patent risk separately.

      Attribution:
    • lg5689 #1
    • jdswain #1
    • cwillu #1
    • dgellow #1

In plain english

Berne Convention
An international treaty that sets baseline copyright rules across many countries, including automatic copyright for qualifying works.
BSD
Berkeley Software Distribution, a family of Unix-like open source operating systems distinct from Linux.
Creative Commons
A family of licenses that lets creators pre-authorize some kinds of reuse of their work.
derivative work
A new work based on an existing copyrighted work, such as a translation, adaptation, or remix, which may still require permission from the original rights holder.
EU
European Union, the political and economic union of member countries in Europe.
GPL
General Public License, a copyleft software license that requires derivative works to be distributed under the same license terms.
MIT
A permissive open source software license that allows broad reuse with minimal conditions.
provenance
Information about where a piece of text or data came from and who or what produced it.
public domain
Material that is not protected by copyright, so anyone can use it without needing permission.

Reference links

Case law and legal background

  • Monkey selfie copyright dispute
    Used as a precedent analogy for nonhuman creators and copyright limits.
  • Work for hire
    Referenced to explain how film and employment-related authorship gets assigned in some jurisdictions.
  • Trap street
    Mentioned as an analogy for planting detectable quirks to prove copying.

AI detection and watermarking

Copyright criticism and reform

Related commentary and prior discussion

Examples and analogies