✨ AI policy, PR template, updated contribution guide and code of conduct (#1045)

* ✨ New AI usage policy, PR template, contribution guide

* 🐞 Fix links in code of conduct

* 🐞 Remove repetitive wording

* 📄 Minor updates

* 📄 Minor updates

* 📄 Minor updates

* ✨ Update PR template

---------

Co-authored-by: Kami <kamibusinessinquirers@gmail.com>

Author: mrkai77

.github/PULL_REQUEST_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_pull_request_template_enabled: false

.github/pull_request_template.md

@@ -0,0 +1,33 @@
+## Description
+
+<!--- Describe your changes in detail -->
+<!--- Why is this change required? What problem does it solve? -->
+
+Fixes #(issue) <!-- If applicable -->
+
+## How has this been tested?
+
+<!-- Describe the tests that you ran to verify your changes -->
+<!-- Provide relevant instructions so we can test it on our side too -->
+<!-- Make sure to also list any relevant details for your test configuration, such as your macOS version -->
+
+- [ ] Test A
+- [ ] Test B
+
+<details><summary><h2>Screenshots (if appropriate)</h2></summary>
+
+<!-- Images go below this line -->
+<!-- Screenshots are highly recommended for any UI-related change -->
+
+</details>
+
+## Checklist:
+
+- [ ] I have performed a self-review of my own code
+- [ ] I have made corresponding changes to the documentation if applicable
+- [ ] I have no unrelated changes in this PR.
+
+## Please describe to which degree, if any, an LLM was used in creating this pull request.
+
+<!-- Ensure that this complies with Loop's AI usage policy -->
+<!-- If no AI assistance was used, please answer "N/A" -->

AI_POLICY.md

@@ -0,0 +1,57 @@
+# AI usage policy
+
+The Loop project has strict rules for AI usage.
+
+All AI usage in any form must be disclosed. You must state the tool you used (for example, Claude, ChatGPT, GitHub Copilot, Cursor) and describe how the work was AI-assisted. If we suspect that you have automatically used a tool to open a pull request-such as when the code fails in obvious ways, or when your responses to review comments do not feel human-we may try to verify that you are a human contributor through specific questions. If you fail to respond, refuse to engage, or cannot reasonably demonstrate understanding, your pull request may be closed and further actions may be taken in line with this policy and the broader policies of the Loop repository.
+
+AI-assisted pull requests must be fully verified by a human. You are responsible for ensuring that AI-suggested changes actually work. You must manually review all AI-generated code rather than pasting unreviewed output, and you must not submit code for platforms, environments, or configurations you cannot personally run or test. Pull requests that clearly contain untested or hypothetical code may be closed without detailed review.
+
+Issues and discussions may use AI assistance but must have a full human in the loop. You must have read and understood everything you are posting, edited AI output for accuracy, relevance, and brevity, and verified any claims of fact or provided citations where appropriate. AI is very good at being overly verbose and including noise that distracts from the main point, so you are expected to do the work of trimming this down before submitting.
+
+No AI-generated media is allowed. Only text and code are acceptable AI-generated content, and only when they comply with the rest of this policy.
+
+These rules apply only to outside contributions to Loop. Maintainers are exempt from these rules and may use AI tools at their discretion. They are expected to exercise good judgment, validate AI output, and remain accountable for changes they approve or merge.
+
+## Not allowed
+
+The following are not allowed under this policy:
+
+- Undisclosed AI usage in any part of a contribution.  
+- Pull requests with AI-generated code that is clearly untested, does not build, or targets platforms or environments you cannot run yourself.  
+- AI-generated media of any kind, including images, diagrams, audio, and video.  
+- Bulk-dumped AI output with little or no human editing.  
+- Using AI to repeatedly reframe ideas that have already been rejected by maintainers.  
+- Automatic or scripted generation of pull requests or comments that you do not personally review, understand, and stand behind.
+
+## Contributor checklist for AI usage
+
+Before submitting, confirm that:
+
+- You have disclosed any AI usage, including which tools were used and how you used them.  
+- Your pull request references an accepted issue, unless maintainers have explicitly allowed otherwise for trivial fixes.  
+- You have manually reviewed and edited all AI-generated content.  
+- You have run the relevant tests or manual checks appropriate for your changes.  
+- You have not included any AI-generated media.  
+- You understand and can explain any code or text you are submitting.
+
+## There are humans here
+
+Loop is maintained by humans.
+
+Every discussion, issue, and pull request is read and reviewed by people, sometimes with the help of tools. That review time is limited and valuable. When low-effort or unqualified work is submitted-especially large amounts of AI-generated content-it shifts the burden of validation onto maintainers.
+
+AI can only be useful here when the person using it takes responsibility for the output: understanding what it does, checking that it is correct, and presenting it clearly. If you use AI, you are still fully responsible for the quality, correctness, and tone of everything you submit.
+
+Treat maintainers’ time with respect by doing the hard work yourself: understand the codebase, validate AI suggestions, and send focused, high-quality contributions.
+
+## AI is welcome here
+
+Some parts of Loop have been developed with the help of AI, and maintainers may actively use AI tools as part of their workflow. As a project, we consider AI to be a valuable tool.
+
+This strict AI policy is not anti-AI. It exists because many people currently using AI lack the experience or context to validate its output. The main risk is not the tools themselves, but unqualified usage that produces incorrect, noisy, or misleading contributions.
+
+We include this section to be transparent about how AI is used in Loop, for people who may disagree with it, and to address the misconception that this policy is anti-AI in nature.
+
+## Attribution
+
+This AI policy takes inspiration from the [Ghostty project's AI policy](https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md) and has been tailored specifically for this project. Any adjustments or interpretations are made solely by the maintainers of Loop and do not reflect the positions or policies of the Ghostty project.

CODE_OF_CONDUCT.md

@@ -1,45 +1,83 @@
-# Contributor Covenant Code of Conduct
+# Contributor Covenant 3.0 Code of Conduct
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we, as contributors and maintainers, pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+We pledge to make our community welcoming, safe, and equitable for all.
 
-## Our Standards
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
 
-Examples of behavior that contribute to creating a positive environment include:
+## Encouraged Behaviors
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
 
-Examples of unacceptable behavior by participants include:
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
 
-- The use of sexualized language or imagery and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
 
-## Our Responsibilities
+## Restricted Behaviors
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
 
-## Scope
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **contact [@MrKai77](https://github.com/MrKai77) or [@SenpaiHunters](https://github.com/SenpaiHunters).**
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are handled directly with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
 
-## Enforcement
+## Addressing and Repairing Harm
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [@MrKai77](https://github.com/MrKai77), [@SenpaiHunters](https://github.com/SenpaiHunters), or [@Soft-Bred](https://github.com/Soft-Bred). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A written warning from the Community Moderators.
+   3) Repair: Examples of repair include a written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at [Contributor Covenant Version 1.4, code of conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html).
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
 
-For answers to common questions about this code of conduct, see [Contributor Covenant FAQ](https://www.contributor-covenant.org/faq).
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).