> 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/fund11-docs/project-onboarding/proof-of-life-pol-verifiers/pol-verifiers-checklist.md). # PoL Verifiers Checklist Have you? * [ ] Joined the [Pol Verifier Telegram ](https://t.me/+drg21NLNpX81MzI8)group? * [ ] Confirmed all details of your PoL Verifiers group to Catalyst? * [ ] Found four available 1.5 hour meeting slots in your diary during 20 February to 1st March for Proof of Life meetings in UTC timezone format? * [ ] Has the group leader submitted this form with the meeting slots you have scheduled? * [ ] Submitted this [form ](https://forms.gle/iXsqDPfMggjCqwxT7)with the meeting slots you have scheduled? * [ ] Confirmed at least two PoL Verifiers group members will participate in the Proof of Life meetings? * [ ] Informed your project teams of the time/date of the Proof of Life meetings? * [ ] 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 3 March 2024 EOD UTC (this means we can start onboarding finalization process on Monday 4th March) * [ ] 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/fund11-docs/project-onboarding/proof-of-life-pol-verifiers/pol-verifiers-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.