> 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/ct-checklist.md).
# CT Checklist
* [ ] Confirmed all details of your Challenge Team to Catalyst?
* [ ] Found four available 1.5 hour meeting slots in your diary during 26 September to 2nd October for Proof of Life meetings in UTC timezone format?
* [ ] Confirmed at least two CT members will participate in the Proof of Life meetings?
* [ ] Created your Challenge Team Communication Hub (Telegram/Discord, etc.) and shared an invitation to FPs?
* [ ] Submitted this[ form](https://forms.gle/4zcRNcBAoQqEZZqC9) with the meeting slots you have scheduled?
* [ ] Received the contact details of your funded projects from the Catalyst team?
* If not, please email
* [ ] Informed your project teams of the time/date of the Proof of Life meetings?
* [ ] Have you completed your proof of life meetings with all your funded projects?
* [ ] Have you updated the Proof of Life validation spreadsheet sent to you, confirming that you are satisfied that proof of life has been confirmed?.
* [ ] Have you emailed to confirm that you have completed POL for all your projects?. The deadline is 2nd October 2023 EOD
* [ ] Have you informed Catalyst of any projects that you were not able to meet with to confirm PoL?
---
# 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/ct-checklist.md?ask=&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.