# Challenges and Tasks

Challenges are the tasks you complete inside μLearn to build real skills and earn Karma. Everything starts here.

Most learning systems ask you to consume content.μLearn asks you to do something with it. A challenge is a real task something you build, write, design, research, or solve. It has a clear brief. It has a quality bar. And it has a real output at the end that you submit for validation.

That output is your Proof of Work.\
That Proof of Work earns you Karma.\
Everything in μLearn starts with a challenge.

### <mark style="color:$primary;">Where Challenges Live</mark>

Every challenge lives inside an **Interest Group** a domain-specific community built around a shared skill or field.

You don't get assigned challenges. You choose them. You walk into your Interest Group, browse the task library, pick something that matches your current level and curiosity, and start. That choice is intentional. Ownership of the task is what makes the learning stick.

### <mark style="color:$primary;">What a Challenge Looks Like</mark>

Challenges vary by domain and difficulty but every challenge has:

| Element           | What It Means                              |
| ----------------- | ------------------------------------------ |
| **Brief**         | What you need to build or produce          |
| **Domain**        | Which Interest Group it belongs to         |
| **Difficulty**    | Entry, intermediate, or advanced           |
| **Output format** | What you submit file, link, repo, document |
| **Quality bar**   | The minimum standard for validation        |

### <mark style="color:$primary;">Types of Tasks</mark>

Not all tasks look the same. Across μLearn's Interest Groups you'll find:

* **Skill tasks** - build something specific to your domain.
* **Challenge tasks** - competitive or sprint-style with a deadline
* **Project tasks** - longer form outputs with multiple deliverables.
* **Community tasks** - facilitating sessions, mentoring, documentation.
* **Initiative tasks** - tasks tied to specific programs like In 50 Hours or Top 100.

### <mark style="color:$primary;">What Happens After You Complete a Challenge</mark>

You submit your output. It enters the validation queue. Peers or leads review it against the quality bar. If it meets the standard Karma is awarded. If it doesn't you get feedback and revise.

That loop complete, submit, review, revise is the learning.

→ For the full submission and validation process, go to [**Proof of Work**](/core-concepts/proof-of-work.md)**.**

→ To understand what Karma means, go to [**Karma**](/core-concepts/karma.md)**.**

### <mark style="color:$primary;">Where to Find Your First Challenge</mark>

Open your Interest Group. Look for tasks marked as entry-level or beginner-friendly. Pick one that matches something you're genuinely curious about.

Don't wait until you feel ready. The challenge is how you get ready.

[**Go to your Interest Groups →**](https://mulearn.org/interest-groups)


---

# 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/core-concepts/challenges-and-tasks.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.