> For the complete documentation index, see [llms.txt](https://whitepaper-ja.wellthverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper-ja.wellthverse.com/service/architecture.md).

# 3.3 Web2とWeb3の連携構造

WellthVerseの特徴は、Web2（アプリとデバイス）とWeb3（WELVトークンとNFT）を、WellthVerse Portal が「資産化・接続レイヤー」として橋渡しする設計です。

* ユーザーID、Wallet address、製品ID（IoTデバイス）を Portal 上で統合的に管理します。
* 育てたWelminは、Portalに移動するときにNFT化され、Galleryに飾ることでWELV トークン獲得に繋がります。
* Portal 上で NFTをアプリ側へアクティベート(Burn)することで、NFTの能力（レアリティ・成長促進の効果など）がアプリに反映されます。
* 「行動データはアプリで管理・蓄積し、資産化は Portal で行う」
  \
  という役割分離が WellthVerse のコアアーキテクチャです。<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper-ja.wellthverse.com/service/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.