> For the complete documentation index, see [llms.txt](https://ncclabs.gitbook.io/ncc-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ncclabs.gitbook.io/ncc-docs/the-ncc-solution/solution-overview.md).
# Solution Overview
NCC builds a multi-layered value network around real assets, on-chain liquidity and real-world applications. Its core is not a single product, but a set of mutually coordinated infrastructure layers.
Figure 1 ยท The four coordinated layers of the NCC ecosystem
## RWA Infrastructure Layer
The RWA Infrastructure Layer forms NCC's asset foundation. It brings real-world assets, those with yield or value backing, onto the chain through legal structures, third-party auditing, asset custody, oracle synchronization and smart-contract settlement.
The objective is to ensure that on-chain assets have a clear real-world source, verifiable yield logic and traceable state updates.
## Unified Liquidity Engine
The Unified Liquidity Engine is NCC's asset-circulation hub. It is designed for cross-chain coordination, deep liquidity, asset-routing efficiency and institutional-grade execution. Serving RWA tokens, NFTs, consumer-rights assets and other ecosystem assets.
## Marketplace & PayFi Network
The Marketplace hosts digital assets, NFT rights and ecosystem applications. The PayFi network connects real consumer scenarios, partner merchants and on-chain assets. Together they enable digital assets to move from on-chain trading into real-world usage.
## NCC Identity Layer
The NCC Identity Layer is the on-chain identity and access-permission infrastructure. It carries users' ecosystem identity, reputation, activity records, rights status and application access. Providing the identity foundation for the Marketplace, PayFi, governance and ecosystem tasks.
The emphasis of this solution is on "coordination," not simply stacking modules. RWAs without liquidity are difficult to adopt at scale; liquidity without real assets and applications easily falls back into speculative cycles; applications without an identity layer and value records struggle to form long-term user relationships. NCC places these elements in the same network by design.
---
# 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://ncclabs.gitbook.io/ncc-docs/the-ncc-solution/solution-overview.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.