> 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/campus-chapter-playbook/what-is-a-learn-campus-chapter.md).

# What is a µLearn Campus Chapter

A µLearn Campus Chapter is a localized wing of the global µLearn ecosystem that operates on a "Dual-Core Model". It is a functional partnership where student execution meets administrative scaffolding to foster a peer-to-peer learning culture. A chapter is considered valid only when both the student leadership (Execom) and the Institutional Management work in synergy.

### <mark style="color:$primary;">The Dual-Core Model</mark>

**Student Leadership (Execom) - Execution & Leadership**

The Execom operates on the "Lead by Doing" principle, where every administrative role is tied to domain leadership:

* **Student Leads (Campus Lead & Co-Lead):** Strategy, community synergy, and operational execution.
* **Domain Leads (Tech & Creative):** Must actively lead their respective Interest Groups (IGs) and Creative Communities.
* **Alumni & Industry Lead:** Facilitates the "Industry-Bridge" initiatives.

**Institutional Management - Scaffolding & Support**

The institution provides the "Scaffolding" for the student-led ecosystem:

* **Lead Faculty Enabler:** A permanent faculty member who acts as the primary liaison between students and management.
* **Core Team of Enablers:** A multi-departmental faculty committee that ensures µLearn principles are integrated into the broader academic culture.
* **Management Commitment:** Direct support from the Principal/Dean for infrastructure and policy alignment.

→ To understand the full ExCom structure, go to [**Campus ExeCom Structure**](/campus-chapter-playbook/campus-execom-structure.md)

→ To start a new campus chapter, go to [**How to Start a Campus Chapter**](/campus-chapter-playbook/how-to-start-a-campus-chapter.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/campus-chapter-playbook/what-is-a-learn-campus-chapter.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.