> 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/how-an-ig-works.md).

# How an IG Works

### <mark style="color:$primary;">How Does an IG Work?</mark>

Every IG operates through five structural components:

* **Focused Domain Scope:** Each IG has a clear, specific pathway.\
  *Example: The Space IG may focus on satellite systems. The MuV IG may focus on short film production.*
* **Roadmap-Driven Progression:** A documented roadmap breaks learning into progressive stages, maps tasks to µLearn levels, and tracks outcomes.
* **Weekly Office Hours:** Consistent domain sessions ensure continuous engagement, knowledge reinforcement, and milestone alignment.
* **Projects & Challenge Integration:** IGs produce structured outcomes mini-projects, prototypes, open-source tools, or social impact initiatives.
* **Ecosystem Alignment:** IGs coordinate with cluster strategy, Think Tank direction, and other IGs for cross-domain collaboration.

### <mark style="color:$primary;">Where Do IGs Fit?</mark>

IGs primarily operate from Level 4 onward:

<table><thead><tr><th width="198.33331298828125">Level</th><th>Stage</th></tr></thead><tbody><tr><td><strong>Level 1–3</strong></td><td>Foundation &#x26; exploration</td></tr><tr><td><strong>Level 4</strong></td><td>Structured Skill-Up - IGs begin here (domain-specific learning)</td></tr><tr><td><strong>Level 5</strong></td><td>Structured Global Challenges - Project-based tasks in phases</td></tr><tr><td><strong>Level 6</strong></td><td>Project Completion - Tangible proof-of-work (portfolios, open-source, social impact)</td></tr><tr><td><strong>Level 7</strong></td><td>µVerse - Leadership and ecosystem contribution</td></tr></tbody></table>

→ To understand the full level structure, go to [**Levels**](/core-concepts/levels.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/how-an-ig-works.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.