> For the complete documentation index, see [llms.txt](https://whitepaper.muish.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.muish.com/introduction.md).

# Introduction

**MOMM i**s a physics-driven exploration game built on reactive systems and structural progression. One tool—blast, clear, reroute. The world pushes back.

Players navigate layered landscapes of decayed industry and mutated architecture. Every structure is physically interactable. Every reaction follows system logic, not scripts. Progress isn’t given—it’s extracted.

$MUISH, an ERC-20 token, fuels the pressure tool and manages infrastructure refills. Some players spend it, others own the refill stations via NFT-backed assets. Blockchain stays optional—silent unless you seek it.

MOMM is made for players who test systems, not follow paths. The environment responds. What you do with that is the game.


---

# 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://whitepaper.muish.com/introduction.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.