Recursive Companion MCP

# Contributor Covenant Code of Conduct ## Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ## Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community * Using welcoming and inclusive language * Being patient with newcomers and those learning * Acknowledging and crediting the contributions of others ### Technical and Professional Context Given that this project involves cognitive AI systems and decision analysis: * **Technical Integrity**: Present technical findings honestly and acknowledge limitations * **Professional Respect**: Respect diverse technical backgrounds and methodological approaches * **Data Privacy**: Respect privacy in examples and case studies, using anonymized data * **Intellectual Property**: Properly attribute technical sources and contributions * **Methodological Openness**: Welcome discussions about technical approaches while maintaining respectful discourse ### Technical Community Standards * **Code Quality**: Strive for clean, well-documented, and tested code * **Security Awareness**: Prioritize security in all contributions and discussions * **Knowledge Sharing**: Help others learn and grow in their technical skills * **Constructive Code Review**: Provide helpful, specific feedback that helps improve code quality * **Documentation**: Contribute to clear, accurate, and helpful documentation ## Our Responsibilities Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. 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, and will communicate reasons for moderation decisions when appropriate. ## Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. This includes: * **GitHub Repository**: Issues, pull requests, discussions, and code comments * **Communication Channels**: Any official project communication channels * **Events**: Conferences, meetups, or other events where the project is represented * **Professional Settings**: When representing the project in professional contexts * **Technical Communities**: Developer forums, technical discussions, or community events ## Unacceptable Behavior Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or email address, without their explicit permission * Conduct which could reasonably be considered inappropriate in a professional setting * Dismissing or attacking someone for their level of experience or knowledge * Gatekeeping or elitist behavior that discourages participation * Spam or irrelevant promotional content ### Context-Specific Unacceptable Behavior **Technical and Security Issues:** * Sharing or requesting sensitive information (API keys, credentials, personal data) * Deliberately introducing security vulnerabilities * Ignoring security best practices in contributions * Attacking or undermining security measures ## Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. ### Reporting Process If you experience or witness unacceptable behavior, or have any other concerns, please report it by contacting the project maintainers at: * **Email**: code-developer@democratize.technology * **GitHub**: Use the private vulnerability reporting feature for sensitive issues All complaints will be reviewed and investigated promptly and fairly. When reporting, please include: * Your contact information (if you wish to be contacted) * Names of any other people involved (if any) * Description of what happened and when it occurred * Any additional context or evidence that would help with the investigation ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: ### 1. Correction **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. ### 2. Warning **Community Impact**: A violation through a single incident or series of actions. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. ### 3. Temporary Ban **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. ### 4. Permanent Ban **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence**: A permanent ban from any sort of public interaction within the project community. ## Appeals Process If you believe you have been falsely or unfairly accused of violating this Code of Conduct, you may appeal the decision by: 1. Submitting a written appeal to code-developer@democratize.technology within 30 days 2. Including a detailed explanation of why you believe the decision was incorrect 3. Providing any additional context or evidence relevant to your case Appeals will be reviewed by community leaders who were not involved in the original incident or decision. The appeal process aims to be fair and thorough while maintaining community safety. ## Building a Positive Community We encourage all community members to: ### For Everyone * **Be Patient**: Remember that everyone has different experience levels and perspectives * **Be Helpful**: Offer assistance to those who need it, especially newcomers * **Assume Good Intent**: Give people the benefit of the doubt in discussions * **Ask Questions**: Don't hesitate to ask for clarification or help * **Celebrate Success**: Acknowledge and celebrate community achievements and contributions ### For Experienced Contributors * **Mentor Others**: Help newcomers learn and grow in their contributions * **Share Knowledge**: Contribute to documentation and knowledge sharing * **Model Behavior**: Set a positive example for community interaction * **Provide Context**: Help explain technical concepts and project history ### For Maintainers * **Transparent Communication**: Keep the community informed about project decisions * **Fair Review Process**: Ensure all contributions receive fair and timely review * **Inclusive Decision Making**: Consider diverse perspectives in project decisions * **Recognition**: Acknowledge and celebrate community contributions ## Acknowledgment This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. Additional guidance was incorporated from successful open source projects focusing on research, security, and inclusive technical communities. For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations. [homepage]: https://www.contributor-covenant.org [Mozilla CoC]: https://github.com/mozilla/diversity ## Contact Information **Project Maintainers**: code-developer@democratize.technology **Security Issues**: security@democratize.technology **General Questions**: Use [GitHub Discussions](../../discussions) --- **This Code of Conduct is effective as of January 2025 and will be reviewed annually.**