OpenJDK bans AI-written contributions, permits AI-assisted reading, and concedes it cannot tell

This surfaced on Hacker News on July 30 at 52 points and 72 comments about three hours in, hours after a thread on GCC's new AI policy, which made it look like two governance bodies moving in concert. They are not: the OpenJDK document is dated April 9 and is resurfacing because of the GCC news. The policy draws a boundary in an unusual place. Contributions "must not include content generated, in part or in full, by large language models," and the FAQ closes the loophole: ten hand-edited lines out of 100 generated ones is still not contributable. But contributors "may use generative AI tools privately to help comprehend, debug, and review OpenJDK code," and the reason given is empirical, hedge attached: "Anecdotal evidence from other communities suggests that analysis of existing code, rather than creation of new code, is where generative AI tools shine for established projects with large code bases."

The policy also says reliable enforcement is impossible. "In general, reliably distinguishing human-generated content from AI-generated content is impossible," it states, then delegates detection to reviewers anyway on stylistic grounds and commits to a mandatory attestation checkbox on every pull request. The page could not be reopened independently, so these quotations come from a full-text capture at 12:25 EDT; the prohibition and private-use clauses are corroborated against the OpenJDK announce list.

Why it matters: Read yes, write no is a falsifiable claim about where agents pay for themselves, from an institution with a very large codebase, and it cuts against where most factory builders are pushing. The enforcement admission belongs next to item 1: a governing body writing down that its control is undetectable, and shipping the control anyway.