> For the complete documentation index, see [llms.txt](https://docs.adcpcapital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adcpcapital.com/products/rwa-product-series.md). # RWA Product Series (Series 003) > Future product template / integration design. **No implementation exists.** ## Concept Tokenisation creates the digital representation of a real-world asset. ADCP's position is not to compete as another tokenisation platform — it is to govern the financial behaviour around an eligible real-world asset once a legally valid asset or claim already exists: credit, cash-flow rules, reserves, repayment, capital allocation, risk, and evidence. ## One engine, isolated asset series Each property, portfolio, receivable pool, commodity exposure, or other RWA would have its own product series and legal wrapper — its own asset identity, legal issuer/SPV, valuation source, capital ceiling, cash-flow rules, reserve policy, eligibility, fees, credit limits, and jurisdiction. ADCP does not need to issue one generic token backed by unrelated real-world assets; the legal asset or claim would be issued by the appropriate regulated or licensed party, with ADCP recognising and governing the product around it. ## Status No RWA-specific design work exists yet at the architecture-decision level, and no Solidity implementation exists. This page describes intent and direction only — not a scheduled deliverable. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.adcpcapital.com/products/rwa-product-series.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.