# Campus Nodes

A Campus Node is a local implementation of the μLearn protocol inside a college or institution not a club, not a chapter, but a node in a decentralised network running the same system with local leadership.

A single central team cannot activate campuses across the country. And it shouldn't try. Campus Nodes solve this by bringing the μLearn protocol to students where they already are inside their colleges, in their physical spaces, led by people from their own community.

### <mark style="color:$primary;">What a Campus Node Is</mark>

A Campus Node is a local implementation of the μLearn protocol within a college or institution.

It is not a club - clubs are informal, campus-bound, and dependent on a few active members.

It is not a chapter - chapters are branches of a central organisation.

It is a **node in a decentralised network** running the same protocol, in a local context, with local leadership and local ownership.

The protocol is universal. The execution is local.

### <mark style="color:$primary;">What a Campus Node Does</mark>

Every Campus Node is responsible for:

* Onboarding new members to μLearn and their profile
* Activating Interest Groups and Learning Circles on campus
* Organising campus-level events, challenges, and sessions
* Connecting students to initiatives and partner opportunities
* Maintaining community health and protocol compliance
* Reporting campus activity to the core team regularly

### <mark style="color:$primary;">Minimum Conditions to Activate a Node</mark>

A campus can activate a μLearn Node when it meets these minimum conditions:

<table><thead><tr><th width="219">Condition</th><th>Requirement</th></tr></thead><tbody><tr><td><strong>Leadership</strong></td><td>At least one verified Campus Lead</td></tr><tr><td><strong>Community</strong></td><td>Minimum active member threshold</td></tr><tr><td><strong>Activity</strong></td><td>At least one active Interest Group or Learning Circle</td></tr><tr><td><strong>Compliance</strong></td><td>Adherence to μLearn's code of conduct and protocol</td></tr><tr><td><strong>Reporting</strong></td><td>Regular activity reporting to the core team</td></tr></tbody></table>

### <mark style="color:$primary;">MOU Framework</mark>

Active campus chapters graded Level A or Level B can formalise their relationship with μLearn Foundation through a signed MOU.

MOU campuses get:

* Priority registration and slots for all μLearn programs
* Curriculum, IG frameworks, and community support
* Recognition in μLearn's official channels and reports

MOU campuses commit to:

* Dedicating a physical space for student activities
* Allowing μLearn Foundation to host events on campus with prior notice
* Maintaining Level A or B grading to retain MOU status

{% hint style="warning" %}
Manual Intervention: Campus Node activation and deactivation requires core team approval. Contact \[campus onboarding form].
{% endhint %}

### <mark style="color:$primary;">If You Found μLearn Through Your Campus</mark>

You entered through a node. Your Campus Lead activated it. Your campus community runs it.

The experience you have on campus the events, the Learning Circles, the IG sessions is all local execution of the same protocol that runs across every active campus chapter in the network.

→ To understand how to run a Campus Node in full, go to **\[**[**Running μLearn\]**](/campus-chapter-playbook/how-to-start-a-campus-chapter.md)

→ To understand Campus Karma the collective score of your campus, go to **\[**[**Campus Karma**](/core-concepts/campus-nodes.md)**]**


---

# Agent Instructions: 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:

```
GET https://docs.mulearn.org/core-concepts/campus-nodes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.