> 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-11-ecosystem.md).

# Chapter 11 — Ecosystem

Three layers share one asset state machine. DataIPO organizes assets and capital, AICOS organizes intelligent workflows, SimpleChain organizes evidence, state, authorization, and settlement; licensed institutions and formal accounts carry the regulated activities.

## 11.1 DataIPO: the capital formation network

DataIPO is the core protocol and capital formation gateway of the SimpleChain ecosystem. It connects asset originators, professional service firms, licensed financial institutions, qualified investors, custody and settlement services, data and technology providers, and authorized agents, organizing onboarding, documentation, due diligence, structuring, approvals, issuance and financing coordination, post-investment monitoring, and exit. The business lifecycle runs nine steps: onboarding → evidence and data room → research and structuring → legal and compliance path → decision and authorization → execution and delivery → post-investment and continuous disclosure → transfer, redemption, and disposal → archiving and reuse. Issuance, fundraising, trading, custody, clearing, payment, and investment advice are carried by licensed or authorized parties in each jurisdiction.

## 11.2 AICOS: the AI Capital OS

AICOS sits at the hub of the asset and capital workflow. It takes in structured and unstructured data and organizes research, valuation, due diligence, risk, rule checks, structuring, disclosure preparation, post-investment monitoring, and agent collaboration. Every output carries its source, model version, rule version, owner, and approval status. The boundary with SimpleChain stays fixed: AICOS computes, orchestrates, explains, and advances tasks; SimpleChain preserves verifiable evidence references, asset state, policy versions, authorization scopes, execution receipts, and audit relations. AICOS may propose state updates; controlled asset state changes only when authorization and preconditions are met.

| AICOS output                               | Protocol object                    | Verification focus                                                 |
| ------------------------------------------ | ---------------------------------- | ------------------------------------------------------------------ |
| Parsed data and evidence lists             | EvidenceEnvelope                   | Source, attestor, time, validity, privacy class                    |
| Research and state-update proposals        | AssetStateRecord / LifecycleEvent  | Evidence references, before/after state, owner, dispute flags      |
| Rule checks and approvals                  | PolicyProfile                      | Jurisdiction, scope, version, formal basis, approver               |
| Agent tasks and permissions                | AgentAuthorization                 | Principal, allowed actions, limits, validity, revocation           |
| Execution packages                         | PCTEnvelope                        | Intent, state, evidence, credentials, authorization, nonce, expiry |
| Post-investment and reconciliation results | SettlementReceipt / LifecycleEvent | Asset leg, cash leg, external receipts, state change               |

AICOS must express uncertainty and refuse automation: with insufficient evidence, policy conflicts, expired credentials, model disagreement, risk thresholds triggered, or open disputes, the flow enters pending, human review, or suspension. Model output stays separate from fact records, and model updates may not silently change historical conclusions.

| Control point              | AI / agent may carry                                          | Responsible party must carry                                                |
| -------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Data and research          | Parsing, retrieval, synthesis, comparison, gap identification | Confirming formal sources, correcting high-risk facts, approving disclosure |
| Valuation and risk         | Model computation, scenarios, alerts                          | Adopting valuations, confirming assumptions, bearing professional duty      |
| Compliance workflow        | Reading policy, checking credentials, generating task lists   | Legal classification, exemption selection, filings, final approval          |
| Trade preparation          | Generating restricted instructions, verifying preconditions   | Wallet or account signing, custody instructions, fund disposal              |
| Post-investment monitoring | Continuous reading, anomaly detection, task triggering        | Handling major events, dispute decisions, external reporting                |

## 11.3 Roles and protocol support

| Participant                             | Contribution                                                          | Protocol support needed                                 |
| --------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------- |
| Asset originators and issuance partners | Assets, data, rights documents, operating and cashflow responsibility | Identity, evidence, state, disclosure, event management |

| Participant                                  | Contribution                                                              | Protocol support needed                                              |
| -------------------------------------------- | ------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Licensed financial institutions              | Admission, accounts, issuance, trading, custody, payment, clearing        | Policies, credentials, authorization, interfaces, receipts, audit    |
| Legal, audit, rating, and verification firms | Professional judgment, attestation, reports, continuous review            | Attestor roles, credentials, evidence packages, versions, revocation |
| Data and IoT providers                       | Operating, device, market, and risk data                                  | Source, Oracle, GranularHash, TDS                                    |
| Validators and institutional nodes           | Consensus, data domains, controlled execution domains                     | Staking, slashing, node permission model                             |
| Developers and applications                  | Research, asset management, monitoring, workflow and interface innovation | API/SDK, object specifications, tests, governance                    |
| Human users and authorized agents            | Decisions, task execution, monitoring, collaboration                      | Minimal permissions, PCT, signing boundaries, receipts               |

## 11.4 Product and service forms

Protocol components (EvidenceEnvelope, Asset State, PolicyProfile, PCT, authorization and settlement receipts); enterprise and institutional interfaces (nodes or controlled connections, API/SDK, event subscriptions, identity and credential integration); trusted data services (TDS, Granular Data, attestation, access audit, verifiable export); asset templates (industry fields, evidence requirements, state dimensions, and process controls on the common object base); compliance collaboration (CaaS policy management, SLC clause mapping, credential verification, human approval routing); agent tooling (restricted query, analysis, preparation, submission, receipt, and audit interfaces); private or institutional deployment (controlled data and execution domains under the governance and interoperability rules).

## 11.5 Network effects

As one Asset ID accumulates evidence and state through onboarding, research, approval, execution, settlement, and post-investment, institutions reuse the context that exists. New data and events surface through AICOS and drive review; execution results flow back into TASM, building a continuous asset history. One event stream does four jobs: due diligence and underwriting, risk pricing, on-chain credit, and agent readability. The network effect comes from standard objects being adopted repeatedly by more responsible parties; the event schema, attestation pipeline, rating model, subordination parameters, and disclosure cadence built for the first asset class migrate to adjacent industries without rebuilding.

> **Ecosystem claim**
>
> DataIPO's line is "AWA takes shape here"; SimpleChain's line is "the native chain of AWA." The three layers are three entrances to one asset state machine.


---

# 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-11-ecosystem.md?ask=<question>&goal=<user_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.