> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/readme/for-circle-stewards/section-2-preparing-for-the-first-circle/checklist-preparing-for-your-first-circle.md).

# Checklist: Preparing for Your First Circle

* [ ] Read Sections 1–3 of the guidebook: familiarise yourself with Logos, Circles, and winnable issues.
* [ ] Book a venue and arrange snacks and drinks for attendees.
* [ ] Create a Luma page following the provided guidelines.
* [ ] Make a social post announcing your Circle.
* [ ] Share the Luma link with local contacts and relevant community groups.
* [ ] Print the Logos Zine and Circles brochure with the QR code to register their contact.
* [ ] Set the agenda and prepare talking points on local issues for the winnable issue discussion.
* [ ] Submit your invoice by the 15th of the month for reimbursement by the end of the month.


---

# 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://circles.logos.co/readme/for-circle-stewards/section-2-preparing-for-the-first-circle/checklist-preparing-for-your-first-circle.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.