AI · 15 October 2026
Linux kernel drops AI disclosure rule for contributor accountability
The Linux kernel project has dropped its requirement that contributors disclose AI tool use. Linus Torvalds said contributors must understand their code, whatever tools they used to produce it.
What happened
The Linux kernel project has dropped its requirement that contributors disclose their use of AI tools, according to reporting by The Register. The change was framed by Linus Torvalds, who said contributors must understand their code, whatever tools they used to produce it.
The shift moves the kernel's contribution policy away from asking how code was made and towards asking whether the person submitting it can stand behind it. For a project of this scale and influence, that is a notable change in how AI-assisted work is governed in open-source development.
Why it matters
AI coding assistants have made it easier to generate patches quickly, and that speed creates a governance question. Mandatory disclosure treats the tool as the risk. Torvalds' framing places the risk on understanding and accountability: a maintainer reviewing a change needs to know that the contributor grasps what it does, how it fits the wider codebase and what it might break.
For leaders in digital transformation and AI adoption, the lesson extends well beyond open source. Organisations that rely on AI-generated work need review processes that test comprehension and ownership, not just provenance. Declarations of tool use may tell a reviewer very little about whether the output is sound, and they can quietly add friction for the people doing the work.
The Renascence take
Most coverage of this story will read it as a relaxing of rules. We see it as a redesign of the signal. A disclosure requirement is an experience like any other: it asks people to perform a ritual that adds effort without necessarily improving the outcome the process is meant to protect.
The real design question is not "who used AI?" but "who can explain this change under review?" Teams that replace provenance checks with comprehension checks, such as clear ownership, short written rationales and reviewers who can probe the logic, get more signal for less ceremony. Operators should audit their own AI disclosure rules and ask whether each one measures quality or merely makes people feel accountable. If it is the second, it is theatre, and it will be the first thing people game.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in AI
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


