> 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/litepaper-v0.3.md).

# Litepaper v0.3

#### Abstract

ValueQube is a TradFi x DeFi qAsset protocol. It turns investable exposures such as equities, ETFs, treasuries, RWAs, quantitative strategies, and on-chain yield into readable account certificates.

The core object is the **qAsset Certificate**: an AI-readable Financial Passport for every investable exposure. A qAsset records what the user entered, when the position was confirmed, how reference value is formed, what risk labels apply, how fees and distributions are handled, and which redemption or exit rules govern the account.

**$54Q** is the ValueQube platform token. It supports incentives, governance, liquidity, data services, ecosystem participation, and protocol-level value feedback. It is not a qAsset vault share and does not represent underlying strategy returns. **qPower** is the contribution-weight system used to measure eligible strategy participation and long-term $54Q holding behavior.

The purpose of this v0.3 litepaper is to define the first public structure of ValueQube: why qAsset exists, how the 54-Facet Financial Qube organizes strategy access, how AI makes account state readable, and where the protocol boundaries remain.

#### What To Remember

**Finance does not need another unreadable balance. It needs a certificate layer that can explain what the balance means.**

#### Scope Of v0.3

This version defines ValueQube at the protocol-account layer. It is not a complete legal document, product manual, token listing document, or final technical specification. Its job is to make the first public architecture clear enough for builders, early users, partners, and community members to understand the same object.

| Question                    | v0.3 Answer                                                                                                                |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| What is the main primitive? | qAsset Certificate                                                                                                         |
| What does it represent?     | A readable account record for an investable exposure                                                                       |
| What does AI read?          | Asset type, reference value, risk labels, fee state, distribution state, redemption rules, and user authorization boundary |
| What does $54Q do?          | Coordinates incentives, governance, liquidity, data services, and ecosystem participation                                  |
| What does qPower measure?   | Eligible contribution weight, not cash yield                                                                               |

The standard for this litepaper is simple: every important object must have a role, a value path, and a boundary. If a term cannot explain what it records, who acts on it, and what it does not promise, it does not belong in the core protocol vocabulary.


---

# 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/litepaper-v0.3.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.