{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigemtfqki7hl73dfxagarzisraktmgnmf6s5w7f2ohmvben4i245q",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfj3mde2lgo2"
  },
  "path": "/t/contributor-responsibility-and-review-cost-in-the-age-of-code-generation/24010#post_16",
  "publishedAt": "2026-02-23T05:24:53.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "In practice the same way they already are today: through reviewer judgment, reputation, and access control over time.\n\n“Accountability” here doesn’t mean legal liability; it means that a GitHub identity accrues trust (or loses it) based on the quality and maintainability of past contributions. Review scrutiny, rejection, loss of reviewer goodwill, and eventually restricted access are the existing mechanisms.\n\nThe statement is meant to make that implicit reality explicit, not to introduce a new enforcement model.",
  "title": "Contributor Responsibility and Review Cost in the Age of Code Generation"
}