{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicxyoku4jdsqkyl6ozyv5ssgelmklxr4txzk2qoafggvqyqbwctqu",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3metg5vbaxzd2"
  },
  "path": "/t/contributor-responsibility-and-review-cost-in-the-age-of-code-generation/24010#post_1",
  "publishedAt": "2026-02-14T15:59:33.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "hiya! this is my first post here. I’d like to start a discussion about contributor responsibility and review cost in the context of AI-assisted code generation\n\nThere have been periodic discussions about whether Rust should regulate or restrict AI-assisted contributions. I want to argue that this framing is both unenforceable and unnecessary\n\nIt is not possible to reliably determine whether a contribution was generated by a human, an AI, or a mixture of tools. Attempting to regulate usage rather than outcomes incentivizes superficial compliance and does not scale.\n\nInstead, I propose that Rust explicitly treat _review cost_ and _contributor responsibility_ as first-class concerns:\n\n  * Contributors are fully responsible for the correctness, safety, licensing, and maintainability of any code they submit, regardless of tooling used.\n  * All contributions must be human-readable and explainable by the submitter.\n  * Review time is a limited resource; submissions that impose excessive review cost may be rejected on that basis alone.\n  * Repeatedly submitting low-signal or high-cost changes should lead to escalating consequences.\n\n\n\nThis mirrors long-standing open-source norms: tools do not submit patches, people do. If a contributor cannot justify or maintain generated output, that output does not belong in the project. This approach avoids unenforceable tool policing while preserving Rust’s standards for correctness and long-term maintainability. I’m interested in feedback on whether this framing would be a useful clarification of existing norms, and whether it should eventually be formalized as contribution guidance or policy.",
  "title": "Contributor Responsibility and Review Cost in the Age of Code Generation"
}