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

# Introduction

Welcome to the Official Whitepaper for the MILTON token.

Milton Empire brings together digital entertainment, luxury products, real estate and media. MILTON is the utility token the team is developing for access and participation across these businesses.

* [Ecosystem](/ecosystem/milton-empire.md): the platform and its products.
* [MILTON Token](/milton-token/overview.md): token utility, allocation and release terms.
* [Rewards Programme](/rewards-programme/overview.md): Uni-Level commissions and the Legends Pool.
* [Glossary](/reference/glossary.md): terms used across these pages.
* [Community Channels](/reference/socials.md): where to follow and contact Milton Empire.

To take part, create an account on [the Milton platform](/ecosystem/platform.md) and buy a token pack.

{% hint style="warning" %}
This is a working document. The team updates it as the project develops, and the content and structure will change.

Last updated 17 September 2026. [About this documentation](/reference/about.md) describes what these pages cover. Questions: [Telegram](https://t.me/miltonempire) or <info@miltonempire.com>.
{% endhint %}


---

# 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.miltonempire.com/readme.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.