logoalt Hacker News

patentatt • yesterday at 5:02 PM • 7 replies • view on HN

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.


Replies

crote • yesterday at 6:49 PM

> 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".

➕ show 1 reply
bayindirh • yesterday at 5:09 PM

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...

➕ show 3 replies
Lerc • yesterday at 6:38 PM

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)

➕ show 3 replies
thfuran • yesterday at 5:17 PM

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.

➕ show 1 reply
loeg • yesterday at 7:07 PM

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.

rcxdude • yesterday at 5:59 PM

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.

RRRA • yesterday at 5:44 PM

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.

➕ show 2 replies