> 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-4-post-circle/checklist-post-event.md).

# Checklist: Post Event

* [ ] Post an update on the Logos Forum about how your Circle went.
* [ ] Send a thank-you message in your group chat, including a link to your forum post for those who want to engage there.
* [ ] Reach out 1:1 to standout participants to discuss taking on a steward role in the Circle.
* [ ] Set up the Luma page for your next Circle as soon as possible, and share the link in your group chat so people know when and where the next meeting is.
* [ ] If a local topic had strong agreement, reach out to relevant people or organisations already working on that issue to explore collaboration, or invite them to the next Circle to discuss the topic in more depth.
* [ ] Join the Online Logos Circle X Space (Tuesdays, 7 PM UTC) to share updates with the broader Logos community and discuss what your Circle is working on.


---

# 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://circles.logos.co/readme/for-circle-stewards/section-4-post-circle/checklist-post-event.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.