> For the complete documentation index, see [llms.txt](https://vitaprotocol.gitbook.io/vita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitaprotocol.gitbook.io/vita/vita-protocol/tkunomikusu/mu-ci.md).

# 目 次

Contents

* **PRELUDE** — [重要なリスク開示および免責事項](/vita/vita-protocol/tkunomikusu/narisukuoyobi.md)
* **第一章** — [モデル総覧：一つの河の全行程](/vita/vita-protocol/tkunomikusu/moderu.md)
* **第二章** — [トークン・パラメータと創世アロケーション](/vita/vita-protocol/tkunomikusu/tkunparamtatoarokshon.md)
* **第三章** — [創世スタッキング：百層のボンディングカーブ](/vita/vita-protocol/tkunomikusu/sutakkingu.md)
* **第四章** — [タワークリスタル：発行・取得・起動](/vita/vita-protocol/tkunomikusu/tawkurisutaru.md)
* **第五章** — [Gas 分流と初期流動性](/vita/vita-protocol/tkunomikusu/gas-to.md)
* **第六章** — [タワーネットワーク：フラクタル構造と貢献ウェイト](/vita/vita-protocol/tkunomikusu/tawnettowkufurakutarutoweito.md)
* **第七章** — [ネットワーク配当：内部エネルギー循環](/vita/vita-protocol/tkunomikusu/nettowkuenerug.md)
* **第八章** — [BTC 配当プール：外部価値の還元](/vita/vita-protocol/tkunomikusu/btc-pruno.md)
* **第九章** — [四段階ステートマシン](/vita/vita-protocol/tkunomikusu/suttomashin.md)
* **第十章** — [モデルの安全性と透明性](/vita/vita-protocol/tkunomikusu/moderunoto.md)
* **終 章** — [総括 · 全パラメータ一覧](/vita/vita-protocol/tkunomikusu/toparamta.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://vitaprotocol.gitbook.io/vita/vita-protocol/tkunomikusu/mu-ci.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.