> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/community-and-contributing/community-standards.md). # Community Standards Community Standards define the shared agreements that keep the Guardian ecosystem consistent, trustworthy, and legible to contributors at every level — from new policy authors to platform engineers. They exist because an open-source project grows fastest when contributors can orient themselves quickly. A well-defined policy standard, a predictable documentation structure, and a visible record of platform decisions reduce the cost of contribution and raise the quality floor across the board. ### What's here * **Guardian Policy Standards (GPS)** — requirements for policies to be accepted into the Methodology Library, covering science-based claims, verifiability, and documentation completeness. * **Guardian System Standards (GSS)** — engineering standards for Guardian platform components. * **Documentation Standards** — how to write and structure pages in this documentation site, including page type definitions and templates. * **RFCs** — design documents capturing ideas and decisions made during platform development, kept here for record keeping. --- # 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://guardian.hedera.com/docs/develop/community-and-contributing/community-standards.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.