> 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/challenge-teams-ct/what-do-you-need-to-do.md).

# What do you need to do?

There are two key tasks for CTs at the onboarding stage  - 

1. Confirm Proof of Life with your project teams (Deadline to complete the PoL [meeting schedule form ](https://forms.gle/mvmkfyboVWvFLzfJ9)is 20 September 2023)
2. Inform Catalyst once you have confirmed Proof of Life with all of your projectsI

### Immediate tasks 

* You must confirm Proof of Life (PoL) with your project teams.
  * You can conduct these meetings as you see fit, provided all the requirements outlined in this document are met.
* Without a PoL funded project teams will not receive funding, so this is a critical and essential part of your role during onboarding. 
* You are more than welcome to attend the Funded Projects Town Hall meeting set formally by IO to set the scene for Funded Projects (this is NOT a PoL meeting)
  * [F10 Onboarding Session A](https://us06web.zoom.us/meeting/register/tZwvdOyhrTkrGtIBcVDQQI83i_gJ0d-fUihp) - 8 AM UTC - 26 September 2023 
  * [F10 Onboarding Session B](https://us06web.zoom.us/meeting/register/tZApdeGorT8vG9VR7JQTcvneqz_HGgQkA8Pv) - 5 PM UTC - 26 September 2023 


---

# 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/previous-funds/fund10-docs/project-onboarding/challenge-teams-ct/what-do-you-need-to-do.md?ask=<question>&goal=<user_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.