> For the complete documentation index, see [llms.txt](https://docs.wlth.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wlth.xyz/community/code-of-conduct.md). # Code of Conduct Part of being a good citizen is that we have have responsibilities as well as rights, we have duties, not just entitlements. That is the meaning of community. That, friends, is the price of belonging. As a collective, we - * Learn together * Participate together * Grow together We share a common cause, and we are all going in the same direction - albeit each of us is moving at our own speeds and with our own ideas of the fastest / best route to get there. We aspire to be warm and welcoming, open, collaborative and informative - but at a minimum we require civilised, honest, and constructive discourse. Let’s keep discussions on point and fact-based where possible. Let’s try prevent emotions running away with us and distorting issues and events. Let’s be cooperative and supportive. Let’s help, not hinder. Community Code of Conduct: * Be respectful to all other users, including the mods and staff * Respect the Community Values outlined in the Manifesto * No hate speech, bullying, trolling or ad hominem attacks * Think critically, and act with compassion * No FUD without evidence * Try to keep topics on-point * Try keep it SFW * Have fun! Repeated violations of this code of conduct or acting in contradiction of the values outlines in the WLTH Manifesto may result in warnings, suspensions and even permanent bans. Believe. Belong, but Behave 😛 --- # 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://docs.wlth.xyz/community/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.