# WellthVerse White Paper

## WellthVerse White Paper

- [1. はじめに](https://whitepaper-ja.wellthverse.com/introduction.md)
- [2. WellthVerseの世界観とビジョン](https://whitepaper-ja.wellthverse.com/vision.md)
- [3. サービス構成とユーザー導線](https://whitepaper-ja.wellthverse.com/service.md)
- [3.1 ユーザーの参加フロー](https://whitepaper-ja.wellthverse.com/service/userflow.md)
- [3.2 主要構成サービス一覧](https://whitepaper-ja.wellthverse.com/service/modules.md)
- [3.3 Web2とWeb3の連携構造](https://whitepaper-ja.wellthverse.com/service/architecture.md)
- [3.4 ユーザーの参加インセンティブ](https://whitepaper-ja.wellthverse.com/service/incentives.md)
- [4.WELVトークンとエコシステム設計](https://whitepaper-ja.wellthverse.com/token.md)
- [4.1 WELVトークンの位置づけ](https://whitepaper-ja.wellthverse.com/token/positioning.md)
- [4.2 WELVトークンの主なユースケース](https://whitepaper-ja.wellthverse.com/token/usecase.md)
- [4.3 WELVトークン設計（Tokenomics）](https://whitepaper-ja.wellthverse.com/token/tokenomics.md)
- [5.NFT活用とマーケットプレイス](https://whitepaper-ja.wellthverse.com/nfts.md)
- [5.1 NFTの役割：ウェルネス経済圏を支える“機能資産”](https://whitepaper-ja.wellthverse.com/nfts/role.md)
- [5.2 NFTの種類と特性](https://whitepaper-ja.wellthverse.com/nfts/types.md)
- [5.3 NFTマーケットプレイス](https://whitepaper-ja.wellthverse.com/nfts/marketplace.md)
- [6. WellthVerse Portalの設計と役割](https://whitepaper-ja.wellthverse.com/portal.md)
- [7. デバイス・データ取得とIoT連携設計](https://whitepaper-ja.wellthverse.com/device.md)
- [7.1 コアデバイス：第一弾 Re・De Ring](https://whitepaper-ja.wellthverse.com/device/redering.md)
- [7.2 拡張計画：その他デバイスとの接続](https://whitepaper-ja.wellthverse.com/device/expansion.md)
- [7.3 Wellness Data NFTの活用の活用](https://whitepaper-ja.wellthverse.com/device/utilization.md)
- [7.4  Wellness Data NFT公開とパートナーオファー機能](https://whitepaper-ja.wellthverse.com/device/datanft.md)
- [8. ロードマップ](https://whitepaper-ja.wellthverse.com/roadmap.md)
- [9. 収益構造とサステナビリティ設計](https://whitepaper-ja.wellthverse.com/revenue.md)
- [9.1 WellthVerseの主要収益源](https://whitepaper-ja.wellthverse.com/revenue/primary.md)
- [9.2 WELVトークン循環による経済圏の収益構造と価値維持](https://whitepaper-ja.wellthverse.com/revenue/circulation.md)
- [9.3 サステナビリティ設計と拡張可能性](https://whitepaper-ja.wellthverse.com/revenue/sustainable.md)
- [10. ガバナンスとセキュリティ設計](https://whitepaper-ja.wellthverse.com/governance.md)
- [10.1 ガバナンス方針：コミュニティと共創する設計](https://whitepaper-ja.wellthverse.com/governance/policy.md)
- [10.2 セキュリティ設計：分散型・実用性・抑止力のバランス](https://whitepaper-ja.wellthverse.com/governance/security.md)
- [10.3 トークン保管とトレジャリー設計](https://whitepaper-ja.wellthverse.com/governance/treasury.md)
- [11. 運営主体とパートナー・コミュニティ体制](https://whitepaper-ja.wellthverse.com/partners.md): コミュニティ
- [12. さいごに](https://whitepaper-ja.wellthverse.com/conclusion.md)
- [留保事項](https://whitepaper-ja.wellthverse.com/disclaimer.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, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on a page URL with the `ask` query parameter:
```
GET https://whitepaper-ja.wellthverse.com/introduction.md?ask=<question>
```
The question should be specific, self-contained, and written in natural language.
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.