> 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/7-kitekuchato.md).

# 7. 技術アーキテクチャと拡張性

<figure><img src="https://445040947-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOxry6bBJam0UPRlzLhGl%2Fuploads%2FvFZ00iW8qcyhO1BFp9jT%2Fshotaueyama_A_sprawling_3D_network_of_modular_server_racks_an_e02a63cc-3112-49c3-83fc-900ac6df8b99_1.png?alt=media&amp;token=9883d73d-8857-4220-86eb-9b88039c7ee1" alt=""><figcaption></figcaption></figure>

GETは、Cardanoブロックチェーンを基盤に、NFTやRWAの発行・取引、ガバナンス、決済など多様な機能を安全かつスケーラブルに提供するためのアーキテクチャを構築しています。本章では、GETエコシステムを支えるシステム設計、チェーン選定の技術的比較、スマートコントラクトの設計思想、将来的な拡張性について詳述します。

***

* [7.1 システム全体構成と3レイヤー構造](https://docs.global-entertainment-token.org/ja/7-kitekuchato/71-shisutemuto3reiy.md)
* [7.2 Cardanoチェーンを選定した理由](https://docs.global-entertainment-token.org/ja/7-kitekuchato/72-cardanochnwoshita.md)
* [7.3 非エンジニア向けの「Web3を意識させない設計思想」](https://docs.global-entertainment-token.org/ja/7-kitekuchato/73-enjiniakenoweb3wosasenai.md)
* [7.4 スマートコントラクトの適用と範囲](https://docs.global-entertainment-token.org/ja/7-kitekuchato/74-sumtokontorakutonoto.md)
* [7.5トークン・決済構造のセキュリティと設計方針](https://docs.global-entertainment-token.org/ja/7-kitekuchato/75tkunnosekyuritito.md)
* [7.6 セキュリティとスケーラビリティ設計](https://docs.global-entertainment-token.org/ja/7-kitekuchato/76-sekyurititosukrabiriti.md)
* [7.7 拡張性と外部連携構想](https://docs.global-entertainment-token.org/ja/7-kitekuchato/77-to.md)


---

# 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/7-kitekuchato.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.
