> 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/the-mulearn-story-and-philosophy/design-principles.md).

# Design Principles

Design principles are operational constraints not aspirational statements. Every design decision in μLearn is tested against these. When something violates them, it gets changed.

These are operational constraints not aspirational statements.The difference matters. Aspirational statements describe what an organisation wishes were true. Operational constraints describe how the organisation actually makes decisions.

<mark style="color:$primary;">**Open by default.**</mark>

No application required. No gatekeeping. No prerequisites. Anyone can join, explore, and participate from day one. The only thing that determines your standing in the ecosystem is what you contribute.

<mark style="color:$primary;">**Activity-based learning.**</mark>

Every learning experience in μLearn is anchored in a task, challenge, or real-world output. Theory is introduced in the context of doing not as a prerequisite to it.The task is the curriculum. The submission is the assessment. The peer review is the feedback loop.

<mark style="color:$primary;">**Decentralised participation.**</mark>

No single team runs μLearn. Campus Nodes, Interest Group leads, Learning Circle facilitators, and volunteers operate autonomously within the shared protocol.The core team sets the protocol and maintains the infrastructure. This is what makes μLearn scalable without becoming bureaucratic and resilient without depending on any single point of control.

<mark style="color:$primary;">**Gamified motivation.**</mark>

Karma Points, leaderboards, tier-based progression, and milestone recognition are the motivation architecture.The gamification in μLearn is meaningful, not decorative. Every point earned represents validated output not engagement theatre.

<mark style="color:$primary;">**Verifiable contribution.**</mark>

Every Proof of Work is logged, validated, and tied to a profile. A learner's profile is not something they fill in it is a record the ecosystem builds for them through their validated contributions.

<mark style="color:$primary;">**Local autonomy, shared protocol.**</mark>

Each campus node, Interest Group, and Learning Circle runs its own culture, pace, and focus. But all of them operate on the same underlying framework.The protocol is universal. The execution is local.

<mark style="color:$primary;">**Human-centred, not platform-centred.**</mark>

When a design decision has to choose between what is better for the platform and what is better for the learner μLearn chooses the learner.This is not a values statement. It is a governance commitment.


---

# 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/the-mulearn-story-and-philosophy/design-principles.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.