> 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/ja/9-rdomappu.md).

# 9. 開発・展開ロードマップ

GETプロジェクトは、Web3とエンターテイメントの融合を通じて、トークン経済がリアルな文化や創作活動に接続する未来を実現するため、段階的かつ実用重視のロードマップを策定しています。

本章では、2025年から2027年にかけての開発ステップと、GETが構想する長期的なビジョンを「3つの軸」に沿って整理します。

* 技術的進化（Platform / Wallet / Marketplace）
* 経済圏の拡大（GET Pay / NFT / RWA / ステーキング）
* 文化的・社会的発展（GET City / アカデミー / グローバル展開）

***

* [9.1 フェーズ1（〜2025年3月）｜基盤整備とローンチ](https://docs.global-entertainment-token.org/ja/9-rdomappu/91-fzu120253tornchi.md)
* [9.2 フェーズ2（〜2025年9月）｜エコシステム構築と初期市場参入](https://docs.global-entertainment-token.org/ja/9-rdomappu/92-fzu220259ekoshisutemuto.md)
* [9.3 フェーズ3（〜2026年3月）｜ユースケース拡張とDAO運営の確立](https://docs.global-entertainment-token.org/ja/9-rdomappu/93-fzu320263ysuksutodaono.md)
* [9.4 フェーズ4（〜2027年3月）｜共創型経済圏のグローバル拡張](https://docs.global-entertainment-token.org/ja/9-rdomappu/94-fzu420273nogurbaru.md)
* [9.5 将来の戦略的拡張構想（2027年4月以降）](https://docs.global-entertainment-token.org/ja/9-rdomappu/95-no20274.md)
* [9.6 ロードマップ設計の基本理念](https://docs.global-entertainment-token.org/ja/9-rdomappu/96-rdomappuno.md)

<br>


---

# 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/ja/9-rdomappu.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.
