> 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/roles-and-responsibilities/think-tank.md).

# Think Tank

The Think Tank is the most credible role in the μLearn ecosystem. Not because it is the most senior. But because it cannot be gamed, applied for, or accumulated into. It is **earned through sustained contribution** and recognised by the core team when three conditions are met simultaneously.

### <mark style="color:$primary;">What Think Tank Members Do</mark>

Think Tank members are the **face and backbone of their Interest Group.**

They do three things:

**Define the PoW** - they design the tasks, challenges, and quality standards for their domain. What counts as valid Proof of Work in that IG is determined by them. They work closely with IG Leads to ensure the task library reflects real industry standards.

**Validate the PoW** - they review and validate high-stakes submissions. Their domain expertise gives the validation credibility that peer review and even Lead review alone cannot provide.

**Represent the IG** - they are the face of the Interest Group to the outside world. When a company asks "who is setting the standard here?" the answer is the Think Tank.

### <mark style="color:$primary;">How to Earn Think Tank Recognition</mark>

Think Tank is not a role you apply for. It is a role the community and core team recognise when three conditions are met:

**Involvement in the mentoring process** - demonstrated, sustained commitment to developing others. Not occasional advice. Consistent mentoring over time.

**Active community presence** - consistently engaged in μLearn as a community member. Not a passive external expert who shows up for validation. Someone who is in the community, visible, contributing.

**Industry proficiency** - recognised domain expertise that is current, deep, and verifiable. The kind of expertise that makes the community trust your quality bar.

All three must be present. One or two is not enough.

> **Manual Intervention:** Think Tank recognition is assessed and awarded by the core team. There is no application form. Nominations can be raised by IG Leads via \[IG governance form].

### <mark style="color:$primary;">Why This Role Cannot Be Gamed</mark>

Most roles in μLearn have Karma thresholds or assessment criteria that a determined person can work toward systematically. Think Tank cannot be worked toward in that way. Because the three conditions sustained mentoring, active presence, verified expertise require time, consistency, and genuine domain depth that no shortcut can replicate.

You cannot fake sustained mentoring. You cannot fake active community presence over months. You cannot fake the kind of industry expertise that makes your quality bar trustworthy. That is why Think Tank is the most credible role in the ecosystem. And that credibility is what makes the entire IG task library and validation system trustworthy.

→ To understand how Think Tank connects to IG validation, go to [**Validation**](/core-concepts/validation.md)

→ To understand how IG task libraries are structured, go to [**Interest Groups**](/core-concepts/interest-groups.md)


---

# 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/roles-and-responsibilities/think-tank.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.