> 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/6-web3toux/64-nomatomeweb29toiue.md).

# 6.4 設計思想のまとめ：「Web2.9」という答え

<figure><img src="https://445040947-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOxry6bBJam0UPRlzLhGl%2Fuploads%2FARFc8NhTp5dhasf6OjXq%2Fshotaueyama_A_monumental_3D_conceptual_sculpture_composed_of__9fc7f130-350a-4368-b881-7b21279e2aa9_1.png?alt=media&amp;token=c2774a69-a011-45f8-ab7b-0566fc73c409" alt=""><figcaption></figcaption></figure>

GETは、以下のような思想に基づいて設計されています。

<table><thead><tr><th width="267.3349609375">設計原則</th><th>実装例</th></tr></thead><tbody><tr><td>Web2に近いUX</td><td>SNS的なUI、QRコード決済、リアルイベント連携</td></tr><tr><td>Web3の透明性と分配性</td><td>ガバナンス投票／NFT二次流通ロイヤリティ／スマートコントラクトによる収益処理</td></tr><tr><td>Web2.0 → Web3.0 の“あいだ”を埋める橋</td><td>GET Pay／GET Miles／Wallet接続だけで完結する統合構造</td></tr></tbody></table>

このように、GETが目指すのは“Web2.9”のような中間領域です。 ユーザーに「Web3だからできること」を感じさせるのではなく、“いつの間にかWeb3を体験していた”という感覚こそが、GETにとっての理想的UXです。


---

# 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/6-web3toux/64-nomatomeweb29toiue.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.
