# The Core Commandments

**TLDR:** 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.

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

Your goal is to build a strong, student-driven, and impact-oriented chapter. By focusing on consistency, collaboration, and the grading milestones, you ensure sustainable growth and meaningful learning for every student on your campus.


---

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