> 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/core-concepts/campus-karma.md).

# Campus Karma

Campus Karma is the collective contribution score of an entire campus chapter used to rank chapters across cities, states, and nationally. It's not individual. It's what your whole campus builds together.

Every individual in μLearn has a personal Karma score across six dimensions. But every campus chapter also has a collective score **Campus Karma** built from the combined contributions of every member on that campus.

Campus Karma is not portable. It doesn't follow any individual. It belongs to the campus. It represents what the community built together.

### <mark style="color:$primary;">What Campus Karma Measures</mark>

Campus Karma is a collective signal of how active, contributing, and engaged a campus community is within the μLearn ecosystem. It answers one question:

*Which campuses are building real communities not just signing up members?*

### <mark style="color:$primary;">What Contributes to Campus Karma</mark>

Every activity your campus community runs contributes to the collective score:

* Member task completions and PoW submissions
* Events organised on campus
* Learning Circles run by campus members
* Interest Group participation and challenges
* Initiatives hosted or participated in by campus members
* Mentoring and volunteering activities by campus members

The more your campus community contributes the higher the collective Campus Karma.

### <mark style="color:$primary;">How Campus Karma is Used</mark>

Campus Karma powers the campus leaderboard ranking chapters across three levels:

**City level** - which campus in your city is most active?

**State level** - which campus in your state is building the strongest community?

**National level** - which campuses across India are setting the standard?

This ranking is public. It's visible to students, companies, institutions, and government bodies.

A campus with high Campus Karma signals something specific to every stakeholder:

* **To students** - this is a campus where real things happen
* **To companies** - this is a talent pool worth paying attention to
* **To institutions** - this is a community worth investing in
* **To government** - this is a model worth replicating

### <mark style="color:$primary;">The Competitive Layer</mark>

Campus Karma is intentionally competitive.Not in a harmful way but in the way that makes campus communities stay active, run more events, push members to contribute, and celebrate collective wins publicly.

It is the mechanism that keeps campus nodes healthy over time not just at launch, but consistently. A campus that stops contributing sees its Campus Karma stagnate relative to peers. A campus that keeps building sees its ranking rise and its students access more opportunities as a result.

→ For full Campus Karma guidelines and grading criteria, go to [**Campus Grading Framework**](/campus-chapter-playbook/campus-grading-framework.md)

→ To understand individual Karma dimensions, go to [**Karma**](/core-concepts/karma.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/core-concepts/campus-karma.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.