> For the complete documentation index, see [llms.txt](https://munia-protocol.gitbook.io/muniaprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://munia-protocol.gitbook.io/muniaprotocol/problem-overview.md).

# Problem Overview

### **No shared economy for decentralized learning**

Education communities are fragmented and siloed. There is no common protocol or currency that connects learners, creators, and partners — value stays locked inside closed systems.

### **Engagement collapses after token launches**

Many learn-to-earn tokens spike at launch, then lose utility. Without persistent use-cases, communities fragment and tokens become speculative assets rather than functional currency.

### **Skill verification is inconsistent**

Self-directed learning lacks portable, trusted proof. Employers, DAOs, and partners need reliable on-chain signals to accept skills at scale.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://munia-protocol.gitbook.io/muniaprotocol/problem-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
