The Cognitive Laundromat
Clean Room Engineering, Semantic Plagiarism, and the Crisis of Academic Originality
This post follows my standard early access schedule: paid subscribers today, free for everyone on April 21.
In early March 2026, a website called Malus began circulating through developer forums and open-source communities with a pitch so brazen it stopped people mid-scroll. “Finally,” the site announced, “liberation from open-source license obligations.” The premise was simple: tell the service which open-source software your product relies on, and Malus’s AI systems would remove the license by independently recreating every component from scratch. One set of AI agents would analyze only public documentation, producing a detailed functional specification containing no code. A completely separate set of agents, which had never communicated with the first, would build the software anew. The resulting code would arrive under MalusCorp’s proprietary license, which had zero attribution requirements and zero obligation to share improvements. In other words, it had zero legal strings of any kind.
The project around this fictional company grew out of a presentation by Dylan Ayery and Mike Nolan at FOSDEM 2026, the annual free software conference in Brussels, titled with characteristic bluntness: “Let’s end open source together with this one simple trick.” Malus by MalusCorp was satire, a deliberately provocative thought experiment designed to demonstrate how AI-driven reverse engineering could render open-source licensing unenforceable. The name of the service had hinted at its purpose, as “malus” is Latin for “bad” or “harmful.” Commenters on Hacker News captured the prevailing mood. “I almost went crazy until I realized it was satire,” wrote one; “I understand this is satire,” replied another, “but in six months it might not be so far from reality.”
The reason Malus landed so hard was that reality had already proved the joke prophetic. Just days before the site went viral, a real controversy erupted over a widely used piece of software called chardet, a Python library downloaded millions or times per month. Dan Blanchard, who had maintained the project for over a decade, used Anthropic’s Claude Code to rewrite the entire library from scratch in five days. He then changed its license, removing the original requirement that anyone building on the code must share their improvements under the same terms.
His argument was straightforward. Since the AI had produced entirely new code, the old license no longer applied. Mark Pilgrim, chardet’s original creator, who had largely withdrawn from public life since 2011, resurfaced to contest this premise. The maintainers had spent years immersed in the original code, Pilgrim argued, and “adding a fancy code generator into the mix does not somehow grant them any additional rights.” The developer community split. Simon Willison, co-creator of the Django web framework, captured the uncertainty when he wrote he was leaning toward the rewrite being legitimate, but that the arguments on both sides were “entirely credible.”
What strikes me most about this sequence of events is that the core operation Malus satirized and Blanchard actually performed is identical in structure to something students do every day. Take someone else’s work. Extract the underlying ideas. Regenerate a new version that looks nothing like the original. Claim it as your own. In the software world, this process has a name, a legal history, and a body of case law stretching back four decades. It is called “clean room engineering,” and its migration from corporate law into the educational landscape represents one of the most consequential, and least discussed, threats to academic integrity that educators currently face.
The architecture of the information firewall
The clean room concept has a specific and revealing history, one that illuminates why its educational implications are so troubling.
