> For the complete documentation index, see [llms.txt](https://docs.ontorium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ontorium.io/vision/roadmap.md). # Roadmap Ontorium is designed to expand in phases across its three layers. This phased approach reflects the logic of the stack itself. The base asset foundation must be established first, financial utility must then be built on top of it, and user-facing applications must ultimately convert that infrastructure into practical access and distribution. ### Phase 1: Asset Layer Foundation The first phase focuses on establishing the Asset Layer through **OXAU.** This phase is centered on bringing physical gold on-chain in a form that is trusted, redeemable, and financially usable. The primary objective is to create a credible base asset that can support the rest of the stack. This includes: * establishing the structure of the on-chain gold asset, * defining reserve integrity and backing logic, * creating the operational basis for issuance and redemption. While OXAU serves as the initial asset, \ the Asset Layer is designed to support the onboarding of additional real-world assets over time. This includes assets such as commodities, structured products, and other verifiable off-chain assets, \ which can be introduced under the same framework of custody, verification, and redeemability. By starting with gold as a universally recognized store of value, \ Ontorium establishes a strong foundation for broader RWA expansion. ### Phase 2: Financial Layer Expansion The second phase focuses on activating the asset within financial markets through AQUA. Once the base asset is established, the next objective is to enable financial utility through lending, borrowing, collateralization, and liquidity access. This phase is intended to transform static asset exposure into productive financial participation. The Financial Layer is critical because it creates the capital efficiency that allows the stack to function as more than a tokenization framework. ### Phase 3: Application Layer Access The third phase focuses on expanding user access and distribution through AQUA App. At this stage, the objective is to make the underlying stack more usable through user-facing applications for payments, transfers, and yield-oriented financial activity. This phase is where infrastructure becomes productized into practical financial experience. The Application Layer plays a decisive role in adoption because it reduces the friction between protocol design and real-world use. is designed to expand in phases across its three layers. This phased approach reflects the logic of the stack itself. The base asset foundation must be established first, financial utility must then be built on top of it, and user-facing applications must ultimately convert that infrastructure into practical access and distribution. --- # 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://docs.ontorium.io/vision/roadmap.md?ask=&goal= ``` `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.