Rust Adopts LLM Policy for Contributions

The announcement came after months of public discussion in the Rust community about AI-assisted code contributions. In a February post on Rust Internals, contributor atix argued that trying to determine whether a patch was human- or AI-generated would be unreliable. The post instead proposed treating contributor responsibility and review cost as central concerns.

That proposal stated that contributors should remain responsible for submitted code's correctness, safety, licensing, and maintainability regardless of tooling. It also argued that submitters should be able to explain their changes, and that maintainers should be able to reject submissions imposing excessive review cost.

In May, Drew DeVault published a proposed pull request titled "Add an LLM policy for rust-lang/rust." The proposal included moderation rules intended to limit discussion of several broader LLM topics in pull-request comments, including social and economic effects, environmental impacts, copyright status, and moral judgments about LLM users.

The available announcement does not establish whether Rust adopted DeVault's proposal, the contributor-responsibility framing from the Internals discussion, or a different policy. It also does not establish whether the policy restricts generated code, requires disclosure, or sets review procedures.

For maintainers of large open-source codebases, the surrounding discussion reflects a recurring governance problem: provenance-based restrictions can be difficult to enforce, while code review, maintainability, licensing, and accountability remain observable properties of a contribution. The practical significance of Rust's policy will depend on the published rules and how repository maintainers apply them.