> 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/the-origin.md). # 1. The Origin Mondrian did not simply paint grids. He compressed a moving, disorderly world into proportion, boundary, order, and composition. ValueQube starts from the same discipline. Financial markets do not lack assets. They lack a structure that can rearrange assets, quote them, and explain them across account systems. Equities, ETFs, treasuries, RWAs, quantitative strategies, on-chain yield, and AI agents usually live in different custody paths, valuation languages, risk cycles, and user interfaces. Most users see balance changes. They do not always see the origin of the exposure, the confirmation price, the fee path, the distribution logic, or the exit window. The cube gives ValueQube a second language. A cube has finite faces and blocks, yet it can create a wide range of combinations. Its power does not come from infinite complexity. It comes from a limited structure that can carry change. ValueQube applies that discipline to financial accounts: six asset faces and fifty-four value blocks. Each block asks whether the asset type, yield source, risk level, duration, liquidity window, valuation method, fee source, rebalance rule, and user fit can be explained. **Finance is not a list of assets. It is a composition that keeps rotating.** #### From Composition To Account Structure Mondrian matters here because composition is not decoration. Composition decides what can sit next to what, where the boundary is drawn, and how a viewer can understand the whole without seeing chaos. ValueQube uses the same idea for finance: an account should not be a pile of positions, but a structured surface where risk, duration, liquidity, valuation, and action rights can be read together. The cube is therefore not only a brand image. It is a protocol grammar. A face defines an asset domain. A block defines a value question. A rotation defines how the same user account may change when asset state, strategy state, or market state changes. #### The 54-Facet Thesis The 54-Facet Financial Qube does not mean fifty-four products must exist on day one. It means every candidate exposure should pass through a finite set of questions before it becomes visible to users. The protocol should know whether an exposure is liquid or delayed, whether its reference value is market-based or model-based, whether yield is distributed or reinvested, and whether an AI agent can explain the state without pretending to control the outcome. That is the origin story of ValueQube: not art added to finance, but composition applied to account truth. --- # 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/the-origin.md?ask= ``` 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.