> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/ig-playbook/community-engagement-tiers.md).

# Community Engagement Tiers

Every IG is structured into three engagement levels in Core Group, Impact Project Volunteers, and Learning Circle to ensure clarity, participation, and impact.

<mark style="color:$primary;">**Core Group**</mark>\
The strategic leadership circle responsible for planning direction, defining the roadmap, verifying tasks, and ensuring alignment with the broader µLearn ecosystem.

<mark style="color:$primary;">**Impact Project Volunteers**</mark>\
A focused group of active contributors who work on building, executing, and delivering Impact Projects translating ideas into real-world outcomes.

<mark style="color:$primary;">**Learning Circle**</mark>\
The open community space where all learners engage, explore, share ideas, and participate in tasks, sessions, and discussions.

→ To understand how Learning Circles work in full, go to [**Section 8.2 - Learning Circle Playbook**](/core-concepts/learning-circles.md)


---

# 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.mulearn.org/ig-playbook/community-engagement-tiers.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.