> 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/protocol-overview.md).

# 3. Protocol Overview

ValueQube has three primary layers.

| Layer              | Role                                                                                                                            | Boundary                                                                |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| qAsset Certificate | AI-readable Financial Passport for an investable exposure                                                                       | Not a stablecoin and not a generic wrapped asset                        |
| $54Q               | Platform token for incentives, governance, liquidity, data services, ecosystem participation, and protocol-level value feedback | Not a qAsset vault share and not a claim on underlying strategy returns |
| qPower             | Contribution-weight system for eligible strategy participation and long-term $54Q holding                                       | Does not change qAsset account value or redemption rules                |

The user path is straightforward. A qualified user subscribes to a selected strategy with eligible assets such as USDC or USDT. After confirmation, the protocol generates the corresponding qAsset Certificate. The account then updates through reference value, distribution state, fee state, reinvestment state, redemption window, and qPower contribution records.

The protocol's design principle is separation. qAsset records the user's strategy account. $54Q belongs to the platform layer. qPower measures contribution weight. AI reads and explains account state, but critical actions require user confirmation.

#### Account Lifecycle

The protocol is easier to understand as a state machine.

| Step      | User / Protocol Action                                  | State Created                                  |
| --------- | ------------------------------------------------------- | ---------------------------------------------- |
| Discover  | User reviews an eligible strategy                       | Strategy description, risk label, access rules |
| Subscribe | User commits eligible assets                            | Subscription record                            |
| Confirm   | Protocol confirms batch and reference value             | Unit record and confirmation price             |
| Issue     | qAsset Certificate is generated                         | AI-readable account object                     |
| Update    | Reference value, fees, distributions, and events update | Account state history                          |
| Explain   | Interface or AI reads the state                         | Report, risk explanation, action draft         |
| Exit      | User requests redemption when rules allow               | Queue, confirmation, and settlement state      |

#### Why Separation Matters

The separation among qAsset, $54Q, and qPower prevents the system from mixing three different meanings. qAsset is the account record. $54Q is the platform-token layer. qPower is a contribution-weight measure. Once those layers are mixed, a user may mistake platform incentives for strategy returns or confuse contribution weight with redemption value. ValueQube is designed to make that confusion harder, not easier.


---

# 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/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.