AI guidelines doc

docs/community/ai-tooling-policy.md

@@ -0,0 +1,18 @@
+# Guidelines for AI-assisted Contributions
+
+The Apache Wayang community welcomes the use of AI and generative tooling as part of the contribution process, provided contributors follow the guidelines below. These guidelines align with the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html).
+
+1. **Verify licensing compliance.** AI-generated code may inadvertently reproduce copyrighted material. Before submitting, ensure the output does not include content that conflicts with the [Apache 2.0 License](https://www.apache.org/licenses/LICENSE-2.0) or the [ASF 3rd Party Licensing Policy](https://www.apache.org/legal/resolved.html).
+
+2. **Understand what you submit.** If you cannot explain why the code works, do not submit it. You are accountable for bugs, security issues, and license violations in your contribution.
+
+3. **Disclose AI tool usage in commits.** When any part of a contribution was generated or significantly assisted by an AI tool, include a `Generated-by:` token in the commit message. For example:
+   ```
+   Fix null pointer in JdbcExecutor
+
+   Generated-by: GitHub Copilot
+   ```
+
+4. **Keep PR discussions human.** When participating in PR discussions, e.g., code review comments, questions, clarifications, and responses, the content must be written by a human, not generated by an AI tool. If an AI tool (such as GitHub Copilot) posts a comment, it must be clearly attributed as such and not presented as the contributor's own words. This ensures that code review remains a genuine exchange between people, preserving the quality, accountability, and community trust that Apache Wayang depends on.
+
+*These guidelines will be updated as AI tooling and the legal landscape around it continue to evolve. Questions or suggestions can be raised on the [dev mailing list](https://wayang.apache.org/docs/community/mailinglist).*