> 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/fund13-docs/project-onboarding/milestone-reviewers-guides/milestone-reviewers-onboarding-meetings/onboarding-session-b.md). # Onboarding session B **Presentation slides** - link [here](https://docs.google.com/presentation/d/1TbHzDj1T_fAAC5v1Rl8uBgN-dTjrhJ4yGC_CxiH3QEU/edit?usp=sharing) **Video recording** - link [here](https://drive.google.com/file/d/1vSbdi_I5E-ViITJJl2xWrl10Ez4FSbGW/view?usp=drive_link) **Video timestamps:** 0:00 Intro and Agenda 1:56 Key Dates 04:25 What is Statement of Milestones (SoM)? 05:09 What is Proof of Achievement (PoA)? 05:43 Milestone Module 08:56 Your Role as a Milestone Reviewer 14:35 Best Practices 16:42 Milestone Reviewer Rewards 17:56 Q\&A **Q\&A questions with timestamps:** 18:09 What are the major changes since fund 10 for Milestone Review process? 22:37 How many projects per reviewer this fund? 23:09 What happens if we decide to take a vacation with no access to the internet for a few days? 24:28 For non-coding related PoAs and relied on documentation as output, if the evidence of the submitted PoA shows a high level of Al and/or GEN- Al and there is crystal clear no such statement is listed in the proposal, indicating the PoA submission will be Al/GEN-AI. Do we rightfully reject it? 29:26 Is there functionality to stop the proposer from submitting the next PoA if the Catalyst team has not approved the previous PoA? So removing the reviewer from the email notification saying they need to do something but it is the Catalyst team that actually needs to still approve 30:31 If the other review has rejected the SoM or PoA for obvious reasons, is it okay to ignore the email in this case or shall we reject it as well? 32:33 A function for second reviewer to not see previous comment to be fair when reviewing --- # 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/fund13-docs/project-onboarding/milestone-reviewers-guides/milestone-reviewers-onboarding-meetings/onboarding-session-b.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.