> 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/positioning-and-roadmap/roadmap.md). # Roadmap ### PHASE 1 · Foundation & Infrastructure *Asset and liquidity base* * RWA framework and Unified Liquidity Engine MVP. * Core contract deployment and initial security audits. * Establish NCC's foundational asset and liquidity base. ### PHASE 2 · Application & Consumer Network *Real-world adoption* * Roll out Marketplace, PayFi network and Identity Layer. * Onboard the merchant network. * Move digital assets from trading into real-world use. ### PHASE 3 · Institutional Expansion *Scaling assets and reach* * Expand RWA asset categories and institutional partnerships. * Cross-chain liquidity and globalized application scenarios. * Evolve from product network into infrastructure network. ### PHASE 4 · Open Governance & Global Network *Ecosystem maturity* * Evolve DAO governance and protocol standardization. * Expand the ecosystem fund and global collaboration network. * Become open infrastructure for real-asset and consumer applications. Each phase is structured around verifiable outcomes. Including asset onboarding capability, liquidity depth, application usage, identity-layer accumulation, merchant-network coverage and governance participation. NCC's roadmap does not chase single-point breakouts. It builds long-term network effects through the gradual maturity of assets, protocol, applications and governance. In the global-expansion phase, NCC will place greater emphasis on standardization. RWA onboarding processes, consumer-rights expression, identity-layer data structures and governance tooling will all be progressively modularized. So that more external developers, partners and application scenarios can integrate with the NCC network at lower cost. --- # 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/positioning-and-roadmap/roadmap.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.