> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/1.-executive-summary.md).

# 1. Executive Summary

<figure><img src="https://707649508-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGcLYARlqDc3ytqX2mvPJ%2Fuploads%2FY3js19wgVCLWdqz3NdKp%2Fimg_2.avif?alt=media&amp;token=1b897b00-af1d-45f3-b203-7e209e8acba6" alt=""><figcaption></figcaption></figure>

## What is GET?

GET (Global Entertainment Token) serves as the cornerstone of the next-generation Web3 entertainment economy, bridging the gap between entertainment sectors such as music, film, sports, and gaming with real-world assets (RWAs) like real estate and tangible goods.

&#x20;

### GET combines

two key characteristics:

・ Governance Token: Empowers community-driven decision-making (DAO voting)

・Utility Token: Seamlessly usable across both real and virtual environments.

&#x20;

Vision: Shaping the Future of Entertainment

GET aims to address the structural challenges inherent in the entertainment industry:

・Lack of transparency in revenue distribution to artists and creators.

・Fans remain passive "consumers" with little active engagement.

・Fragmentation of value across content, experiences, and products.

・Digital assets (NFTs) and real-world assets (live performances, merchandise, RWAs) are disconnected.

Through blockchain technology, GET will reconstruct this landscape around the principles of co-creation and participatory engagement.

&#x20;

GET offers three core values


---

# 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.global-entertainment-token.org/1.-executive-summary.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.
