🌐 pot(main): update .pot from Sphinx

Updated .pot files for 'main' version from Sphinx.

Before: {
  "branch": "main",
  "commit": {
    "date": "2026-01-05 09:37:34 +0100",
    "hash": "e65317acbb5cdd2207d87e44731121f35f5250e5",
    "title": "[ValueTracking] Support ptrtoaddr in computeKnownBits() (#173358)"
  }
}
After: {
  "branch": "main",
  "commit": {
    "date": "2026-02-23 14:14:10 +0530",
    "hash": "84be3259dd470dbd18a5b57847f499aff59c719b",
    "title": "[mlir][Linalg] Allow isaBroadcastOpInterface to accept LinalgOp (#182806)"
  }
}

Created by the GitHub Workflow:

- File: https://github.com/localizethedocs/llvm-docs-l10n/actions/workflows/ci-sphinx-update-pot.yml
- Run: https://github.com/localizethedocs/llvm-docs-l10n/actions/runs/22298869881
- Job: https://github.com/localizethedocs/llvm-docs-l10n/actions/runs/22298869881/job/64501896402

Author: ltdrobot

main/locale/pot/LC_MESSAGES/AIToolPolicy.pot

@@ -0,0 +1,295 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2003-2026, LLVM Project
+# This file is distributed under the same license as the LLVM package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: LLVM main\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2026-02-23 08:56+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../../AIToolPolicy.md:1
+msgid "LLVM AI Tool Use Policy"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:3
+msgid "Policy"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:5
+msgid ""
+"LLVM's policy is that contributors can use whatever tools they would like to "
+"craft their contributions, but there must be a **human in the loop**. "
+"**Contributors must read and review all LLM-generated code or text before "
+"they ask other project members to review it.** The contributor is always the "
+"author and is fully accountable for their contributions. Contributors should "
+"be sufficiently confident that the contribution is high enough quality that "
+"asking for a review is a good use of scarce maintainer time, and they should "
+"be **able to answer questions about their work** during review."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:14
+msgid ""
+"We expect that new contributors will be less confident in their "
+"contributions, and our guidance to them is to **start with small "
+"contributions** that they can fully understand to build confidence. We "
+"aspire to be a welcoming community that helps new contributors grow their "
+"expertise, but learning involves taking small steps, getting feedback, and "
+"iterating. Passing maintainer feedback to an LLM doesn't help anyone grow, "
+"and does not sustain our community."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:21
+msgid ""
+"Contributors are expected to **be transparent and label contributions that "
+"contain substantial amounts of tool-generated content**. Our policy on "
+"labelling is intended to facilitate reviews, and not to track which parts of "
+"LLVM are generated. Contributors should note tool usage in their pull "
+"request description, commit message, or wherever authorship is normally "
+"indicated for the work. For instance, use a commit message trailer like "
+"Assisted-by: <name of code assistant>. This transparency helps the community "
+"develop best practices and understand the role of these new tools."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:21
+msgid ""
+"<name of\n"
+"code assistant>"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:30
+msgid ""
+"This policy includes, but is not limited to, the following kinds of "
+"contributions:"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:33
+msgid "Code, usually in the form of a pull request"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:34
+msgid "RFCs or design proposals"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:35
+msgid "Issues or security vulnerabilities"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:36
+msgid "Comments and feedback on pull requests"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:38
+msgid "Details"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:40
+msgid ""
+"To ensure sufficient self review and understanding of the work, it is "
+"strongly recommended that contributors write PR descriptions themselves (if "
+"needed, using tools for translation or copy-editing). The description should "
+"explain the motivation, implementation approach, expected impact, and any "
+"open questions or uncertainties to the same extent as a contribution made "
+"without tool assistance."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:47
+msgid ""
+"An important implication of this policy is that it bans agents that take "
+"action in our digital spaces without human approval, such as the GitHub "
+"[`@claude` agent](https://github.com/claude/). Similarly, automated review "
+"tools that publish comments without human review are not allowed. However, "
+"an opt-in review tool that **keeps a human in the loop** is acceptable under "
+"this policy. As another example, using an LLM to generate documentation, "
+"which a contributor manually reviews for correctness, edits, and then posts "
+"as a PR, is an approved use of tools under this policy."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:56
+msgid ""
+"AI tools must not be used to fix GitHub issues labelled [`good first issue`]"
+"[good-first-issue]. These issues are generally not urgent, and are intended "
+"to be learning opportunities for new contributors to get familiar with the "
+"codebase. Whether you are a newcomer or not, fully automating the process of "
+"fixing this issue squanders the learning opportunity and doesn't add much "
+"value to the project. **Using AI tools to fix issues labelled as \"good "
+"first issues\" is forbidden**."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:66
+msgid "Extractive Contributions"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:68
+msgid ""
+"The reason for our \"human-in-the-loop\" contribution policy is that "
+"processing patches, PRs, RFCs, and comments to LLVM is not free -- it takes "
+"a lot of maintainer time and energy to review those contributions! Sending "
+"the unreviewed output of an LLM to open source project maintainers "
+"*extracts* work from them in the form of design and code review, so we call "
+"this kind of contribution an \"extractive contribution\"."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:75
+msgid ""
+"Our **golden rule** is that a contribution should be worth more to the "
+"project than the time it takes to review it. These ideas are captured by "
+"this quote from the book [Working in Public][public] by Nadia Eghbal:"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:81
+msgid ""
+"\\\"When attention is being appropriated, producers need to weigh the costs "
+"and benefits of the transaction. To assess whether the appropriation of "
+"attention is net-positive, it's useful to distinguish between *extractive* "
+"and *non-extractive* contributions. Extractive contributions are those where "
+"the marginal cost of reviewing and merging that contribution is greater than "
+"the marginal benefit to the project's producers. In the case of a code "
+"contribution, it might be a pull request that's too complex or unwieldy to "
+"review, given the potential upside.\\\" \\-- Nadia Eghbal"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:90
+msgid ""
+"Prior to the advent of LLMs, open source project maintainers would often "
+"review any and all changes sent to the project simply because posting a "
+"change for review was a sign of interest from a potential long-term "
+"contributor. While new tools enable more development, it shifts effort from "
+"the implementor to the reviewer, and our policy exists to ensure that we "
+"value and do not squander maintainer time."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:97
+msgid ""
+"Reviewing changes from new contributors is part of growing the next "
+"generation of contributors and sustaining the project. We want the LLVM "
+"project to be welcoming and open to aspiring compiler engineers who are "
+"willing to invest time and effort to learn and grow, because growing our "
+"contributor base and recruiting new maintainers helps sustain the project "
+"over the long term. Being open to contributions and [liberally granting "
+"commit access][commit-access] is a big part of how LLVM has grown and "
+"successfully been adopted all across the industry.  We therefore "
+"automatically post a greeting comment to pull requests from new contributors "
+"and encourage maintainers to spend their time to help new contributors learn."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:110
+msgid "Handling Violations"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:112
+msgid ""
+"If a maintainer judges that a contribution doesn't comply with this policy, "
+"they should paste the following response to request changes:"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:120
+msgid ""
+"The best ways to make a change less extractive and more valuable are to "
+"reduce its size or complexity or to increase its usefulness to the "
+"community. These factors are impossible to weigh objectively, and our "
+"project policy leaves this determination up to the maintainers of the "
+"project, i.e. those who are doing the work of sustaining the project."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:126
+msgid ""
+"If or when it becomes clear that a GitHub issue or PR is off-track and not "
+"moving in the right direction, maintainers should apply the `extractive` "
+"label to help other reviewers prioritize their review time."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:130
+msgid ""
+"If a contributor fails to make their change meaningfully less extractive, "
+"maintainers should escalate to the relevant moderation or admin team for the "
+"space (GitHub, Discourse, Discord, etc) to lock the conversation."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:134
+msgid "Copyright"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:136
+msgid ""
+"Artificial intelligence systems raise many questions around copyright that "
+"have yet to be answered. Our policy on AI tools is similar to our copyright "
+"policy: Contributors are responsible for ensuring that they have the right "
+"to contribute code under the terms of our license, typically meaning that "
+"either they, their employer, or their collaborators hold the copyright. "
+"Using AI tools to regenerate copyrighted material does not remove the "
+"copyright, and contributors are responsible for ensuring that such material "
+"does not appear in their contributions. Contributions found to violate this "
+"policy will be removed just like any other offending contribution."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:146
+msgid "Examples"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:148
+msgid ""
+"Here are some examples of contributions that demonstrate how to apply the "
+"principles of this policy:"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:151
+msgid ""
+"[This PR][alive-pr] contains a proof from Alive2, which is a strong signal "
+"of value and correctness."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:153
+msgid ""
+"This [generated documentation][gsym-docs] was reviewed for correctness by a "
+"human before being posted."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:159
+msgid "References"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:161
+msgid "Our policy was informed by experiences in other communities:"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:163
+msgid ""
+"[Fedora Council Policy Proposal: Policy on AI-Assisted Contributions "
+"(fetched 2025-10-01)][fedora]: Some of the text above was copied from the "
+"Fedora project policy proposal, which is licensed under the [Creative "
+"Commons Attribution 4.0 International License][cca]. This link serves as "
+"attribution."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:167
+msgid "[Rust draft policy on burdensome PRs][rust-burdensome]"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:168
+msgid ""
+"[Seth Larson's post][security-slop] on slop security reports in the Python "
+"ecosystem"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:170
+msgid ""
+"The METR paper [Measuring the Impact of Early-2025 AI on Experienced Open-"
+"Source Developer Productivity][metr-paper]."
+msgstr ""
+
+#: ../../../AIToolPolicy.md:172
+msgid "[QEMU bans use of AI content generators][qemu-ban]"
+msgstr ""
+
+#: ../../../AIToolPolicy.md:173
+msgid "[Slop is the new name for unwanted AI-generated content][ai-slop]"
+msgstr ""