> For the complete documentation index, see [llms.txt](https://df-manual.gitbook.io/df-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://df-manual.gitbook.io/df-book/review-circle/faqs.md).
# FAQs
Q: **What does the Review Circle review?**\
A: The Review Circle reviews:
* Eligible proposals
* Milestone submissions from awarded teams
* RFP and ideation proposals & deliverables
Any work tied to funding decisions or milestone payments goes through the Circle.
\
Q: **Who reviews my work?**\
A: Your work is reviewed by assigned members of the Review Circle. Reviewers are selected based on experience, availability, and relevance to the project. Coordinators oversee assignments and final checks.
\
Q: **How are milestones reviewed?**\
A: Once a milestone is submitted, a reviewer evaluates the delivery and submits a review report. After that, a coordinator audits the review before the milestone moves forward in the process.
\
Q: **What criteria are used during reviews?**\
A: Reviews focus on:
* Clarity and completeness
* Feasibility of the work
* Quality of deliverables and evidence
* Alignment with the proposal or RFP
Reviews are based on these criteria, not personal opinion.
\
Q: **How long do Milestone reviews usually take?**\
A: Milestone reviews usually take up to two weeks. In some cases, reviews may take longer if the assigned reviewer is unavailable. In such cases, the milestone is reassigned to another reviewer so the review can continue.
\
Q: **What happens if a milestone is marked incomplete or rejected?**\
A: You’ll receive feedback explaining what’s missing or needs improvement. Once the issues are addressed, the milestone can be resubmitted for review.
\
Q: **Can I question or challenge a review?**\
A: Yes. If something feels unclear or incorrect, raise it through Mattermost. Coordinators will look into the issue and decide if clarification or a second review is needed.
\
Q: **Are reviewers anonymous?**\
A: Reviewers may use pseudonyms. However, all reviews are tracked internally to ensure accountability and consistency.
Q: **How does the Review Circle ensure fairness?**\
A: The Review Circle follows shared guidelines and review criteria. Coordinator audits help maintain consistency across projects and reviewers.
\
Q: **How should teams communicate with the Review Circle?**\
A: All communication happens through Mattermost. Teams should use public channels when possible and private channels only when necessary.
Q: **What is the Review Circle not responsible for?**\
A: The Review Circle does not handle contracts, token payouts, or voting mechanics. Those are managed by other parts of Deep Funding.
---
# 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://df-manual.gitbook.io/df-book/review-circle/faqs.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.