> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund10-docs/how-to-participate-in-community-reviews/community-review-moderation-process-lv2/rules-for-community-moderators-lv2.md). # Rules for Community Moderators (LV2) * All reviews should be provided to voters unless a Community Moderator has good reason not to include it * It is anticipated that many flagged reviews will be approved by Community Moderators and will be included for voters to consider * Moderators are there to provide a sanity check to verify if the flag(s) have raised a valid concern * Moderators should use their best judgment and provide a reason if they agree the flag is valid, meaning that the review should not be included * The majority of reviews will be displayed in the voting application, meaning only those legitimately flagged and tagged by LV2 Moderators will not be included * Simple majority forms consensus about including the review or not. In a scenario whereby 2 moderators (or equal number of moderators on each side of the decision) do not form consensus about including the review or not, then the benefit of the doubt will be given and the review included. * In a scenario where only 1 moderator checked a review, then the Catalyst will fulfill the second necessary moderation * In a scenario where flagged or spot checked reviews go without moderation by either LV2 moderators allocated to check then the Catalyst team will fulfill the moderation duty. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.projectcatalyst.io/previous-funds/fund10-docs/how-to-participate-in-community-reviews/community-review-moderation-process-lv2/rules-for-community-moderators-lv2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.