> 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/catalyst-tools/community-review-module/lv0-and-lv1-review.md).
# LV0 and LV1 Review
### Proposals review
1\. When the review submission period opens, you will have access to the proposals assigned to you. Navigate to the "Allocated proposals" tab to view the list of proposals you are responsible for reviewing
2\. Once you open a specific proposal to review, you will see on the right submission form. You should evaluate the proposal based on three criteria: impact, feasibility and value for money. For each criteria, rate the proposal using a scale of 1 to 5 stars, provide a detailed rationale for your assessment, ensuring that your explanation is at least 200 characters long
3\. Complete your evaluation and submit your review
4\. If you want to review proposals outside of allocation, you may choose from the “Proposals” tab
5\. In the “Community Reviews” tab you will see your submitted reviews. There will be label “Pending moderation” which mean that this review was not yet moderated
### Editing, removing and viewing submitted reviews
**Editing a Review**:
1. If you need to make changes to a submitted review, click the "Edit review" button
2. Make the necessary adjustments and resubmit your review
**Deleting a Review**:
1. If you want, you can delete the review by clicking the "Delete" button
2. This action is irreversible
**Viewing Submitted Reviews**:
1. Navigate to the "Community Review" tab to view a list of all submitted reviews
2. Here, you can see the reviews you have submitted
---
# 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/catalyst-tools/community-review-module/lv0-and-lv1-review.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.
