> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/engage/code-of-conduct.md). # Code of Conduct This Code of Conduct applies to everyone who takes part in the Sunbird RC community — contributors, maintainers, adopters and anyone joining our discussions. Contributing to the project means you agree to uphold these principles. ## Our principles * **Be considerate.** Your work and words affect users and other contributors. Think about how they will land, and remember that many people in this community work in a second or third language. * **Be respectful.** Disagree about ideas, not people. Harassment, personal attacks, and discriminatory or exclusionary language are not acceptable. * **Be available.** If you take on an issue or a review, keep others informed of your progress. If you need to step back, say so, so someone else can pick the work up. * **Be honest.** Be open about what you know and what you don't, credit other people's work, and be upfront about the limitations of your contributions. * **Exercise discretion and confidentiality at appropriate times.** Don't share other people's private information. Report security vulnerabilities privately rather than in public issues, and respect anything shared with you in confidence. ## Where this applies These principles apply in every project space: the Sunbird RC GitHub repositories, GitHub Discussions, Discord, community calls and events. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://rc.sunbird.org/engage/code-of-conduct.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.