> For the complete documentation index, see [llms.txt](https://docs.valueqube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valueqube.io/lite-paper/zh/protocol-overview.md).

# 3. 协议概览

ValueQube 有三层核心结构。

| 层级                 | 作用                                    | 边界                        |
| ------------------ | ------------------------------------- | ------------------------- |
| qAsset Certificate | 可投资敞口的 AI-readable Financial Passport | 不是稳定币，也不是普通 wrapped asset |
| $54Q               | 平台代币，服务激励、治理、流动性、数据服务、生态参与和协议价值回流     | 不是 qAsset 金库份额，也不代表底层策略收益 |
| qPower             | 贡献权重系统，衡量合格策略参与和长期持有 $54Q 的行为         | 不改变 qAsset 账户价值，也不改变赎回规则  |

用户路径应该保持直接。合格用户用 USDC 或 USDT 等合格资产认购选定策略。确认后，协议生成对应的 qAsset Certificate。账户随后通过参考价、分配状态、费用状态、复投状态、赎回窗口和 qPower 贡献记录持续更新。

协议设计原则是分层。qAsset 记录用户的策略账户，$54Q 属于平台层，qPower 衡量贡献权重。AI 读取并解释账户状态，但关键动作必须由用户确认。

#### 账户生命周期

协议可以被理解成一个状态机。

| 步骤        | 用户 / 协议动作             | 生成的状态          |
| --------- | --------------------- | -------------- |
| Discover  | 用户查看合格策略              | 策略说明、风险标签、准入规则 |
| Subscribe | 用户投入合格资产              | 认购记录           |
| Confirm   | 协议确认批次和参考价            | 份额记录与确认价格      |
| Issue     | 生成 qAsset Certificate | AI 可读账户对象      |
| Update    | 参考价、费用、分配和事件更新        | 账户状态历史         |
| Explain   | 界面或 AI 读取状态           | 报告、风险解释、操作草稿   |
| Exit      | 用户在规则允许时发起赎回          | 队列、确认和结算状态     |

#### 为什么必须分层

qAsset、$54Q 和 qPower 的分离，是为了防止系统把三种不同含义混在一起。qAsset 是账户记录，$54Q 是平台代币层，qPower 是贡献权重。一旦三者混同，用户就可能把平台激励误解为策略收益，把贡献权重误解为赎回价值。ValueQube 的设计目标，是让这种误解变难，而不是变容易。


---

# 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:

```
GET https://docs.valueqube.io/lite-paper/zh/protocol-overview.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.