🤖 AI Contribution Policy
We recognize that AI-assisted coding is a powerful tool for modern development.
To ensure the quality, security, and maintainability of our codebases, we’ve established the following guidelines regarding the use of Artificial Intelligence (LLMs, Copilots, etc.).
âś… 1. AI Usage is Permitted
You are not prohibited from using AI tools to help write code, generate documentation, or brainstorm solutions.
We care about the final result: high-quality, functional, and secure code.
🤝 2. The “Human-in-the-Loop” Rule
All contributions must be “vouched for” by a human.
- Human Responsibility: Every commit and Pull Request (PR) must have a primary human author/committer who fully understands every line of code being submitted.
- Vouching: By submitting a PR, you are stating that you have reviewed the AI output, verified its correctness, and take full responsibility for its inclusion in the project.
📝 3. Attribution Recommendations
If a commit or PR is heavily generated or assisted by an AI, we recommend (but don’t strictly require) acknowledging the tool in the commit metadata.
- You can add a trailer to your commit message like so:
Co-authored-by: AI-Assistant <ai-bot@example.com> - Regardless of attribution, the Main Committer must always be a human.
🔍 4. Review Process
- No AI-Only Reviews: Pull Requests can’t be approved or merged based solely on the output of AI-based review tools.
- Human Oversight: A human maintainer or contributor must perform a manual review and “vouch” for the PR before it’s accepted.
âť“ 5. Do I need to declare AI usage?
Not necessarily.
Because our policy requires a human to be the primary committer and “vouchee” for every single line of code.
Therefore the origin of the logic is secondary to the human’s verification of it.
As long as you understand and stand behind the code as if you wrote it yourself, the human verification is perfectly sufficient.
Ensuring our code remains readable, maintainable, and human-verified. 🚀