Hacker News new | past | comments | ask | show | jobs | submit
There is well-established precedent for clean-room design being a defense in copyright infringement of software. The question remains if LLM-assisted design is actually ‘clean’ or not, and it would be fascinating to see the experts debate it.
The problem with these LLMs are they really emitted the same code, verbatim. One scientific library developer was able to emit his code from his repository by typing the beginning of the function name, and the "thing" completed the rest of it, as-is [0].

We can debate clean-room development all day long, and it's fair point, but the pain point is/was reproducing the repo as-is, sans its license and ownership information.

GitHub promised to build tools around its Copilot to find code provenance (e.g.: list of repos with similar code), but they silently dropped all the plans AFAIK, since it'll show how the sausage is made, and nobody wants you to know how that sausage is made.

I stand corrected: They added it, but I don't know at what capacity because I don't use LLM assisted code generation [1].

[0]: https://x.com/docsparse/status/1581461734665367554

[1]: https://github.blog/ai-and-ml/github-copilot/preview-referen...

Not discrediting your work at all and I can’t tell you it applies here.

For copyright to exist there is some burden of proof. If you claim that an LLM verbatim output your code there can be an expensive lawsuit with expert witnesses that would be able to state that the code was bot original enough for copyright to exist in it and a statistical model outputting the code is evidence of that.

In that case you would end up with a very long lawsuit that is expensive to possibly come out with no resolution in the end and be in the hole for 5-6 figures for it.

The copyright system is broken because it only protects those with money so it is a bad legal foundation.

My personal point is there is only 2 licenses of code, closed source or permissive, because if it ever comes to enforcement I cannot possibly go to court and win a case because I will run out of money far earlier than whoever used the code.

Pretty much if someone with your knowledge would have written the same algorithm because it is the obviously correct solution then there is no copyright there because any clean room implementation would be the same code.

loading story #50508859
This feels very outdated. It was certainly an issue around the time of the NYT lawsuit, but I believe the companies responded hard to that "sanitize" their outputs to prevent obvious regurgitation like this. I'd be very surprised if you could reproduce this today.

This doesn't negate your point, but I believe the landscape has changed in response to this point.

loading story #50509076
loading story #50509281
loading story #50509921
That was 4 years ago when the models were much worse and smaller. I'd be curious to see this same experiment tried again.
> The question remains if LLM-assisted design is actually ‘clean’ or not

I genuinely don't understand how one could possibly make that argument.

The entire point of clean-room design is to kill every possibility of copyright infringement before it even starts, by completely separating the source and destination. Everyone who has ever read the copyrighted source is considered "tainted" and may not ever contribute any code to the "clean" destination. The readers and writers are two completely distinct teams, with only the known-clean specification passing between them.

LLMs, on the other hand, are fundamentally nothing more than a "code blender". You mix together giant piles of "tainted" code, and then statistically pull some combined fragments out of it. Following the clean-room legal argument, it should be treated as if everything coming out of it is tainted. There is, by definition, absolutely zero separation between input and output - and the early models verbatim reproducing popular F/LOSS code made that pretty obvious. LLMs are the literal opposite of a clean-room design!

Granted, going for the clean-room approach is overkill - and intentionally so. It is the nuclear option chosen when you believe the risk of getting sued is substantial. It is perfectly possible to write non-infringing code without using a clean-room approach, it is just a lot harder to defend in court when you get sued - be it justifiably or not. But "LLMs are non-clean-room non-infringing" is quite a different argument from "LLMs are clean-room, therefore non-infringing".

I agree with you overall, but it's an interesting question to turn over and contemplate.

>I genuinely don't understand how one could possibly make that argument.

With perhaps a bit of genuine irony inasmuch as it's a real reversal from most of computing history, highly locked down proprietary software might actually be a place where a case could be made even with current LLMs. After all, have any LLMs (or anyone else who hasn't signed an NDA for that matter) ever seen the source code of iOS 27 or other Apple crown jewels for example? So if someone used one LLM to produce the factual spec of a piece of software whose code is not part of its training data, humans to verify it was indeed just an uncopyrightable factual spec, and then a separate isolated freshly initialized LLM to produce something exclusively from said spec, it might well work with respect to that specific target? Like yes, the LLM would be dirty as hell for other stuff, but only the copyright holder can sue. Apple couldn't sue the output on behalf of F/LOSS projects or copyright infringement in general, only with respect to its own.

In principle, I suppose this could also be extended with enough compute power to any arbitrary software. Build an LLM perfectly from scratch with a signed verified training set (which you save) that includes nothing of what you want to CRE, and you should be able to prove that it's "virgin" on that front. Of course in practice that'd mean jumping back in time and be super expensive right now, no current tainted LLM could be a base point. But maybe eventually compute will drop back down in price enough again, and/or meta breakthroughs in training, that for valuable enough CRE targets, someone might create a business around creating "CRE LLMs certifiably and legally/technically provably clean of any copyrighted material related to your target" which would still leave most of the corpus of human works. That could really disrupt a lot of the current regime.

F/LOSS I assume would actually be the most resistant to this in principle due to being insanely hard to not have be part of a core training set in any way.

While this is well established legally, I don't think the principles involved are well understood.

Legally, you cannot steal an idea, because you cannot own an idea. There were sound reasons for making this the case. Those reasons stand up today and are clearly for the public good.

Intellectual property is intended to cover works (copyright), methods (patents), and identity (trademarks). Both works and methods are recognised as expressions of ideas, and in an ideal world should belong to noone as well. This is why copyright and patents expire. Those specific grants of temporary possession are to incentivise more things being done.

The belief that you own something because you thought it up has become common, but it is not beneficial to society. It is a moral value asserted but rarely explored. It is certainly in the interests of the wealthy accumulators of intellectual property to maintain that public perception. The 'You wouldn't download a car' may not have stopped piracy much but as a part of a broader campaign of instilling a value in the public mind it appears to have been massively successful. Those beliefs used to be the corporate opinion, now they are entrenched in the younger generation as they use their anger against the growing wealth inequality to fight against AI in a manner ultimately beneficial to those forces that bought about the wealth inequality.

Movements like the pirate party, open source, the EFF fought against those notions. Often the phrase "Information wants to be free" was used. It is, unfortunately, hard to fight the steady drumbeat of well financed PR firms. As one PR chap once described the process "limited to a very few points and must harp on these in slogans until the last member of the public understands what you want him to understand"

(I apologise for the length of my post, I use comment writing to organise my thoughts on a topic)

"Legally, you cannot steal an idea, because you cannot own an idea"

well patent itself is "claiming" that certain idea/method/invention is yours for certain period of time...

anyway, as for "intellectual property", the courts are 100% on "only human made stuff are to be protected" (sorry even Chimps lost their copyright)

so... court can charge against "human work -> LLM", but won't care about "LLM work -> human / other LLM / etc"

hence, I'd expect zero copyright protection for AI-generated code

loading story #50510423
Patent law doesn't only cover methods, though. It might've worked that way during the Industrial Revolution, but these days a lot of patents are far closer to covering abstract ideas than concrete machines. Software patents are some of the worst offenders here, of course.
loading story #50510463
Ownership itself is rarely beneficial to society. Society however is gaussian and incentives to push the median are broadly equivalent to beneficial / adversarial to society. So then, may I ask:

What do LLMs do to the median?

I don’t really see how anyone could argue in good faith that it’s ‘clean’ if the thing to be re-implemented was in the training data.
loading story #50508830
Clean room is sufficient, but not necessary, btw. Humans can create legally distinct works after reviewing copyrighted code. The same principle probably extends to AI systems -- they have just learned on a much broader corpus than any one human.
You don't necessarily need a clean room implementation to mount a successful defense against copyright infringement in court, though. It just makes some of the arguments a little bit easier.
Under multiple countries interoperability laws, if you have a context to extract a spec, and then have another one who never looked art the code work from that spec to build your own interpretation of your need for that software, that seems pretty clean room to me...

If there are more murky situations where people just keep the same context and end up reusing function structure, program architecture, etc. then yeah, that's not very clean room.

loading story #50509796
loading story #50509226