> 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/initiatives/top100-series.md).

# Top100 Series

The Top 100 Series is an elite recognition and deployment framework selecting the top 100 Coders, Designers, and Makers from the μLearn ecosystem. Peer-validated, proof-of-work backed, globally deployable.

### <mark style="color:$primary;">What It Is</mark>

The Top 100 Series is an elite recognition and deployment framework where the best talent from three critical domains is selected:

* **Top 100 Coders** - Elite software developers, problem solvers, and engineers
* **Top 100 Designers** - Visionary UI/UX experts, brand storytellers, and creatives
* **Top 100 Makers** - Hardware builders, roboticists, and IoT innovators

Together, these become a **super-guild of 300 innovators** who are peer-validated, proof-of-work backed, and globally deployable.

### <mark style="color:$primary;">The Journey to Top 100</mark>

{% stepper %}
{% step %}

### <mark style="color:$primary;">Entry through μLearn</mark>

Join Learning Circles, climb through skill tracks, Karma points, and PoW challenges.
{% endstep %}

{% step %}

### <mark style="color:$primary;">Proof-of-Work Validation</mark>

Showcase real builds apps, prototypes, UI kits. Peer and industry validations strengthen portfolios.
{% endstep %}

{% step %}

### <mark style="color:$primary;">Leaderboards and Industry Challenges</mark>

Regular gigs, problem statements, and competitions push learners to the edge. Leaderboards track progress transparently.
{% endstep %}

{% step %}

### <mark style="color:$primary;">Final Assessment and Curation</mark>

Industry mentors and practitioners evaluate top candidates. Communication, discipline, and professionalism are also assessed.
{% endstep %}

{% step %}

### <mark style="color:$primary;">Becoming Top 100</mark>

Recognition and deployment readiness unlocked. Featured in μLearn's global portfolio. Activated for global gigs and corporate challenges.
{% endstep %}
{% endstepper %}

### <mark style="color:$primary;">Who It's For</mark>

**Students** - Global market visibility. Invitation to premium freelancing projects and cross-border gigs. Portfolio-first credibility.

**Companies** - Curated, elite pool. Access deployable talent for short-term projects, UX testing, startup pilots.

**Academia** - Education 4.0 in practice bridging curriculum with real market validation.

### <mark style="color:$primary;">How to Participate</mark>

Participate actively in your domain's Interest Group. Build consistent PoW. Climb the Karma leaderboard. The top performers are identified and curated you don't apply to be Top 100. You build until you are.

[**View Top 100 →** ](https://mulearn.org/events.)


---

# 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/initiatives/top100-series.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.