> 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/roles-and-responsibilities/learner.md).

# Learner

A learner is anyone who has created a profile and is actively engaging with μLearn. No minimum qualification. No age limit. No domain restriction. Everything in the ecosystem exists to serve your growth.

The learner is the primary actor in μLearn. Everything else the Interest Groups, the Learning Circles, the Karma system, the initiatives exists to serve the learner's growth. A learner is anyone who has created a profile and is actively engaging with the ecosystem. There is no minimum qualification. There is no age limit. There is no domain restriction.

### <mark style="color:$primary;">Your Rights as a Learner</mark>

Every learner in μLearn has the right to:

* **Access** - to all open Interest Groups, Learning Circles, tasks, and challenges
* **Recognition** - to have contributions validated and reflected in their profile
* **Fairness** - to a transparent, consistent Karma and validation system
* **Feedback** - to receive constructive review on every PoW submission
* **Appeal** - to escalate disputes through defined channels
* **Privacy** - to control what is visible on their public profile
* **Opportunity** - to be considered for initiatives based on merit, not connections

### <mark style="color:$primary;">Your Responsibilities as a Learner</mark>

Rights come with responsibilities. Every learner is expected to:

* Submit **honest, original work** as Proof of Work
* Engage in **peer validation** with integrity and care
* Respect the **community code of conduct**
* Maintain **accurate profile information**
* Communicate openly when you need help or cannot meet commitments

### <mark style="color:$primary;">How to Show Up</mark>

* Show up consistently not perfectly, but consistently
* Give feedback the way you'd want to receive it
* Ask questions openly the community learns when you do
* Credit collaborators and sources in your PoW
* Treat every validation you do as seriously as the ones done on your work

### <mark style="color:$primary;">How to Participate</mark>

<table><thead><tr><th width="212.33331298828125">Pathway</th><th>How to Enter</th></tr></thead><tbody><tr><td><strong>Skill Building</strong></td><td>Join an Interest Group, complete tasks</td></tr><tr><td><strong>Peer Learning</strong></td><td>Join or form a Learning Circle</td></tr><tr><td><strong>Challenge-Based</strong></td><td>Participate in IG challenges or initiative sprints</td></tr><tr><td><strong>Event-Based</strong></td><td>Attend Permute, In50Hours, campus events</td></tr><tr><td><strong>Mentorship</strong></td><td>Apply for μMent as a mentee</td></tr><tr><td><strong>Career</strong></td><td>Access Launchpad after Karma threshold</td></tr></tbody></table>

### <mark style="color:$primary;">Growing Beyond Learner</mark>

Being a learner is not a stage you leave. It is the foundation everything else is built on. As you contribute more consistently you naturally move into the Contributor role. As you demonstrate domain expertise and community trust IG Lead or Campus Lead roles open up. As you grow in experience Mentor becomes possible. All of these can happen simultaneously. You don't stop being a learner when you become a Contributor or an IG Lead.

→ To see how learning actually happens, go to [**Section 3 - How μLearn Works**](/how-mulearn-works.md)

→ To understand what your profile records as you grow, go to [**μID**](/core-concepts/mid.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/roles-and-responsibilities/learner.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.