> 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/11-risukutono/115-burandorisuku.md).
# 11.5 ブランド・信用リスク
外部パートナー、コンテンツ提供者、提携プロジェクトによる影響で、プロジェクトの信頼性が毀損される可能性があります。
**主なリスク要因**
* 提携先の不正・不祥事
* コンプライアンス上の懸念による協業停止
* オンチェーン情報と現実の乖離
**対応方針**
* 提携先・IP提供元に対しては信用審査を実施し、契約時に解除条項を明記
* プロジェクトとして提携先に対する柔軟な対応オプションを保持
* RWAとの接続におけるリアル証明の併存モデル（例：所有証書＋NFT）
---
# 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/11-risukutono/115-burandorisuku.md?ask=&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.