> 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/fund9-docs/the-statement-of-milestones-module-fund9-only/using-the-milestone-module/roles-and-responsibilities/milestone-reviewers-using-the-milestone-module/som-process.md).
# SoM process
SoM are reviewed by the respective Milestone Reviewers and Catalyst Team Reviewer during onboarding. Projects do not go LIVE once the Milestone Reviewers and Catalyst Team Reviewer have accepted the SoM.
Milestone Reviewers are asked to review all milestones and supporting information and consider whether the SoM sufficiently lays out a clear path to project delivery based on what the Cardano Community voted for and approved during Project Catalyst’s governance stage.
Once the Milestone Reviewers have reviewed the SoM, they are asked to indicate whether or not the milestones were satisfactory, with supporting comments for the SoM to be included in the project file.
---
# 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/fund9-docs/the-statement-of-milestones-module-fund9-only/using-the-milestone-module/roles-and-responsibilities/milestone-reviewers-using-the-milestone-module/som-process.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.