# Validation

Validation is the trust layer of μLearn the mechanism that makes every Karma point real and every Proof of Work credible. Five validation modes exist, applied based on what you submitted and how high the stakes are.

Karma is only worth something if the system behind it is trustworthy. Validation is what makes it trustworthy. Without validation a Karma score is just a number anyone could claim. With validation every point is backed by a real output, reviewed by a real person or system, against a real quality standard.Validation is not gatekeeping. It is the mechanism that makes μLearn's credibility signal honest.

### <mark style="color:$primary;">The Five Validation Modes</mark>

Not every submission goes through the same review process. The mode depends on what you submitted and how high the stakes are.

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

**Who validates:** Fellow learners within the same IG or Learning Circle

**When it's used:** Standard tasks, routine PoW submissions, LC outputs

**How it works:** Structured review against defined criteria not a casual thumbs up

**Why it exists:** Scales validation across thousands of submissions without a central bottleneck. Also builds the reviewer's own domain judgment reviewing good work makes you better at producing it.

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

**Who validates:** IG Lead or LC Facilitator

**When it's used:** Domain-specific tasks, high-value PoW, edge cases that peers aren't qualified to assess

**How it works:** Expert review against domain quality standards set by the IG Lead

**Why it exists:** Ensures domain integrity. Catches what peer review misses. Maintains the credibility of domain Karma.

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

**Who validates:** Assigned mentor internal or external

**When it's used:** Advanced projects, initiative-level outputs, research work

**How it works:** Deep review with structured feedback not just approval or rejection, but guidance

**Why it exists:** Brings external credibility to advanced work. Elevates the quality bar for the highest-stakes submissions.

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

**Who validates:** Automated platform checks

**When it's used:** Every single submission, at the point of entry before human review begins

**How it works:** Format checks, completeness checks, duplication detection

**Why it exists:** First filter. Prevents low-effort or duplicate submissions from entering the human review queue. Protects reviewers' time and maintains queue integrity.

### <mark style="color:$primary;">Core Team Manual Review</mark>

**Who validates:** μLearn core team

**When it's used:** Disputes, escalations, and edge cases that cannot be resolved at community level

Situations that trigger core team review:

* Karma disputes unresolved at IG Lead level
* PoW submissions that fall outside defined task types
* Validation conflicts between peer and lead reviewers
* Suspected abuse or gaming of the Karma system
* Appeals against rejected submissions

### <mark style="color:$primary;">The Validation Hierarchy</mark>

When in doubt about which validation mode applies follow this hierarchy:

```
System Check (every submission)
        ↓
Peer Review (standard tasks)
        ↓
Lead Review (domain-specific or high-value)
        ↓
Mentor Review (advanced or initiative-level)
        ↓
Core Team (disputes and escalations only)
```

Each level catches what the level before it misses. Together they make the system trustworthy at scale.

### <mark style="color:$primary;">Why Validation Makes Karma Credible</mark>

A Karma score without validation is self-reported data.A Karma score with validation is verified evidence.

The difference matters enormously to every stakeholder who uses Karma as a signal:

* A company using Launchpad to hire trusts that a 5,000 Karma score reflects 5,000 points of validated, peer-reviewed, domain-specific output
* A mentor considering a mentee trusts that the PoW log reflects real work, not claimed work
* A learner trusts that her peers' Karma scores reflect real contribution making the leaderboard meaningful rather than gamed

Validation is what makes all of this possible.

→ To understand how validation connects to Proof of Work submission, go to **\[**[**Proof of Work**](/core-concepts/proof-of-work.md)**]**


---

# 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/validation.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.