> For the complete documentation index, see [llms.txt](https://dataipo.gitbook.io/dataipo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dataipo.gitbook.io/dataipo-docs/whitepaper-center/simplechain-whitepaper/chapter-2-from-rwa-to-awa.md).
# Chapter 2 — From RWA to AWA
RWA was Web3's experiment in financial products; AWA is the next generation of assets, joined to the new productive forces. SimpleChain is built where the three curves meet, and it upgrades the asset form itself.
## 2.1 Definition
AWA (AI World Assets): assets produced by AI-native businesses, metered continuously by machines, grounded in verifiable operating data and cashflow, and readable, priceable, financeable, and manageable by humans and agents together.
As a formula: RWA × AICOS = AWA. RWA supplies the off-chain asset, right, or cashflow; AICOS supplies parsing, rating, pricing, and continuous monitoring; the product is a capital object that both people and machines can read. AWA abbreviates an asset class and may never be used as a token ticker. It creates no new legal asset category; underlying rights remain determined by contracts, SPVs, account control, and applicable law.
## 2.2 Five admission standards
| No. | Standard | Meaning | Protocol anchor |
| --- | -------------------------- | ------------------------------------------------------------------------------------------ | ------------------- |
| 1 | AI-native production | The business runs on AI or automated systems; data is metered at the moment it is produced | Source registry |
| 2 | Machine-metered operations | Usage, delivery, cost, and revenue are metered record by record | Granular Data |
| 3 | Verifiable cashflow | Cashflow can be cross-checked against independent sources and recomputed | EvidenceEnvelope |
| 4 | Continuous trusted state | Asset state keeps updating after issuance | TASM |
| 5 | Capitalizable structure | SPV, waterfall, account control, and post-investment monitoring in place | PolicyProfile / SLC |
An asset qualifies for the AWA reference library when it meets at least the first four standards; the fifth determines which capital paths it can enter.
## 2.3 AWA, RWA, and tokenized securities
RWA describes the broad direction of off-chain assets, rights, or cashflows connecting to digital systems. AWA asks whether the asset has the capabilities of a machine-readable capital object: AI-readable, verifiable, authorizable, continuously manageable. Tokenized securities express securities rights as digital tokens and remain subject to applicable securities law throughout. The three overlap and keep independent definitions.
| Concept | Center of concern | SimpleChain's role |
| -------------------- | ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| RWA | Connecting off-chain facts to digital representation | Organizes evidence, asset identity, state, and lifecycle |
| AWA | A machine-readable capital object priced and financed by humans and agents together | Provides native state, policy, authorization, execution, receipts |
| Tokenized securities | Digital expression and compliant transfer of securities rights | Technical protocol for licensed parties; makes no securities classification of its own |
## 2.4 Three-layer consistency and the nine dimensions
An AWA must stay consistent across its legal, economic, and digital layers. The legal layer states rights, obligations, restrictions, and enforcement mechanisms. The economic layer states value sources, cashflow, risk, and settlement relations. The digital layer states identifiers, evidence, state, policy, authorization, and events. A change in any layer drives review of the others through authorized events. The carrier of the digital layer is SimpleChain's nine-dimensional Asset State.
The nine dimensions of AWA Asset State: identity, evidence, rights, compliance, operations, cashflow, risk, settlement, lifecycle
*Figure 1 The nine-dimensional Asset State of AWA*
## 2.5 Maturity
AWA maturity is assessed continuously and moves with evidence quality, state continuity, rule coverage, settlement verifiability, and governance maturity. The protocol records the satisfaction of each dimension, dependence on human review, disputes, and expired evidence. Maturity describes verifiable coverage; credit ratings, regulatory permissions, and yield judgments are made by the responsible parties under their formal standards.
> **Class claim**
>
> Tokenization is a one-time minting event; an AWA is a running process. The asset changes from a snapshot taken on issuance day into a state stream that updates with the business every day and that humans and machines can both read.
---
# 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://dataipo.gitbook.io/dataipo-docs/whitepaper-center/simplechain-whitepaper/chapter-2-from-rwa-to-awa.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.
