> 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/the-core-commandments.md).

# The Core Commandments

Five non-negotiable rules every campus chapter must follow the official handle format, foundation-generated logo only, all activities free, support through proper channels, and document everything.

*"Quality is not an act, it is a habit. These commandments are the habits that turn a campus chapter into a legacy."*

### <mark style="color:$primary;">Commandment 1 - Official Handle Rule</mark>

All social media handles must follow the format **mulearn.\<campuscode>**. There are no exceptions.

### <mark style="color:$primary;">Commandment 2 - The Campus Logo</mark>

Only use the official, foundation-generated logo for your campus chapter in all communications.

### <mark style="color:$primary;">Commandment 3 - The Free Philosophy</mark>

All µLearn activities must be free. For collaborations where a fee is unavoidable, you must set a merit-based criteria (e.g., Level 5+ or 7000+ Karma) to provide free registrations to top µLearners.

### <mark style="color:$primary;">Commandment 4 - Support Channels</mark>

For any official requests, addressals, or roadblocks, reach out to your District Lead or email <campus@mulearn.org>.

### <mark style="color:$primary;">Commandment 5 - Document Everything</mark>

Maintain clear reports and media files (photos/videos) for every initiative, event, and project on your campus.


---

# 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/the-core-commandments.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.