> 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/how-to-become-a-community-reviewer/community-reviewers-levels/how-do-i-progress-through-the-community-reviewer-levels.md). # How do I progress through the Community Reviewer levels? ## For Fund10 For each previously held Proposal Assessor (PA) ID, based on the past performance of old funds, the relative percentage of valid assessments submitted that were either Excellent OR Good, is a qualifying factor to determine a LV0, LV1, or LV2 Community Review level. This parameter allows setting a minimum % of valid assessments to qualify previously held PA IDs in Fund10. In order to qualify as a LV1 in Fund10, a previously held PA ID must have completed a minimum of 10 reviews with a threshold of at least 70% valid assessments submitted from their total work. In order to qualify as a LV2 in Fund10, this threshold is set at 20 reviews with at least 80% valid assessments submitted from their total work and active participation as PA in the last fund (F9) is required. In Fund10 Cardano Ambassadors have also been invited to participate in LV2 Moderation as they have already been recognized as capable Cardano community contributors, helping encourage others to keep within Cardano Community code of conduct. ## After Fund10 A retrospective should be held to learn how the new Community Review stage operated in practice and determine where the community participation levels can be further refined based on the data collected. This will help to determine what the starting lines and ways to progress through the levels should be for the next funding round. --- # 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.projectcatalyst.io/previous-funds/fund10-docs/how-to-participate-in-community-reviews/how-to-become-a-community-reviewer/community-reviewers-levels/how-do-i-progress-through-the-community-reviewer-levels.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.