> 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/appendix-a-glossary.md). # Appendix A — Glossary Core terms carry one definition across product, technical, legal, and market materials. | Term | Full name | Definition | | ------------------------------ | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | AWA | AI World Assets | Assets produced by AI-native businesses, metered continuously by machines, grounded in verifiable operating data and cashflow, readable, priceable, financeable, and manageable by humans and agents together; an asset-class abbreviation, never a ticker. | | RWA | Real-World Assets | The broad category of off-chain assets, rights, or cashflows connecting to digital systems. | | DataIPO | DataIPO | The core protocol and capital formation network of the SimpleChain ecosystem: onboarding, issuance, allocation, post-investment, institutional coordination. | | SRW | SRW | The native utility token of SimpleChain mainnet: gas, staking and governance, incentives, the settlement unit for CaaS. | | Fact / Price / Industry Oracle | Industry oracles | Oracles modular by data type: operating events, mixed-asset pricing, sector indicators. | | AICOS | AI Capital OS | The AI capital operating system organizing data, models, research, valuation, rules, tasks, human approvals, and post-investment monitoring. | | SimpleChain | SimpleChain | The native chain of AWA: the Trusted Asset Chain for real-world and AI-native capital, the native execution environment for evidence, state, policy, authorization, execution, and receipts. | | PoSA | Proof of Staked Authority | Consensus in which staked validators produce blocks in fixed rotation, with BFT vote finality layered on top. | | Authorized Agent | Authorized Agent | An agent granted defined actions, objects, limits, validity, and review conditions by a principal in verifiable form. | | Asset ID | Asset identifier | The stable cross-system reference for an asset; it proves no rights and no authenticity by itself. | | Asset State | Asset state | The nine-dimensional state vector: identity, evidence, rights, compliance, operations, cashflow, risk, settlement, lifecycle. | | TASM | Trusted Asset State Machine | The state machine managing Asset State transitions by version, evidence, policy, authorization, and events. | | Granular Data | Granular data | Data units split by business semantics, responsibility, time, source, privacy, and update rules. | | GranularHash | Granular hash | The integrity commitment over granular data or canonical data sets; it proves no truth and no legality of content. | | TDS | Trusted Data Space | The partitioned, access-controlled, computable, versioned, and audited space for sensitive asset data. | | Source | Source | The party or system where data, documents, or records are first produced, maintained, or formally published. | | Attestor | Attestor | The party bearing attestation responsibility for a claim within its qualification or mandate, signing verifiably. | | Oracle | Oracle | The service or interface delivering off-chain data, events, or computation results to the protocol under a defined mechanism. | | Credential | Credential | A verifiable statement issued by a formal party proving identity, role, or permission. | | Provenance | Provenance | The traceable relations among data, evidence, derivations, transformations, and responsible parties. | | PolicyProfile | Policy profile | The object describing jurisdiction, asset and offering scope, participant scope, credentials, rule versions, decisions, and responsibility sources. | | CaaS | Compliance as a Service | The compliance layer organizing formal rules, credential verification, decisions, human approvals, and version governance as a service. | | SLC | Smart Legal Contracts | The component connecting formal legal texts, structured conditions, responsible parties, signatures, technical execution, and dispute control points. | | PCT | Proof-Carrying Transaction | The native transaction type carrying asset state, evidence, policy, credentials, authorization, settlement conditions, nonce, expiry, and signatures. | | Term | Full name | Definition | | --------------------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Capital Execution Engine | Capital execution engine | The interfaces and controls that verify and execute controlled intents, connect on-chain and external systems, collect receipts, and trigger state updates. | | Agent-Native Capital Router | Agent-native capital router | The controlled routing layer connecting AICOS, the protocol, and external licensed, custody, and settlement systems by state, policy, account capability, and authorization. | | Verifiable Compliance | Verifiable compliance | A compliance process whose rule sources, scopes, versions, credentials, approvals, validity, and results can all be reviewed. | | Settlement | Settlement | The process by which asset and cash legs deliver, confirm, and reconcile under defined conditions. | | SettlementReceipt | Settlement receipt | The object holding execution identifiers, settlement mode, both legs, on-chain and external receipts, state changes, parties, times, and signatures. | | DvP | Delivery versus Payment | The delivery principle linking asset delivery and payment by condition to reduce principal risk. | | Selective Disclosure | Selective disclosure | The privacy method disclosing only the attributes or proofs verification needs, never the full identity and asset data. | --- # 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/appendix-a-glossary.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.