> 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/project-onboarding/funded-proposers-fp/key-dates.md).

# Key dates

* 20 Sep 2023 Deadline for CT onboarding form
* 21 Sep 2023 - F10 Results Announced
* 21 -22 Sep 2023 - Intro email to Funded Projects (FP)
* 25 Sep - Deadline FP onboarding form
* 26 Sep 2023 - FP Onboarding Celebration / Funded Projects Town Hall (2 AM/PM time slots)
* 26 Sep - 2 Oct 2023 Meetings to provide Proof of Life (PoL)
* 26 Sep 2023 - FP to receive email from Catalyst Team with link to reset password and create a new one in the Milestone Module
* 26 Sep 2023 - FP to check if the number of milestones is correct in the Milestone Module
* 26 Sep - 02 Oct 2023 - Statement of Milestones formulation
* 2 Oct - Test Tx confirmation deadline
* 09 Oct 2023 - Statement of Milestones finalization (inc. approvals)


---

# 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/fund10-docs/project-onboarding/funded-proposers-fp/key-dates.md?ask=<question>&goal=<endgoal>
```

`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.