> 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/trust-security-and-compliance/compliance-risk-management.md). # Compliance & Risk Management Because NCC involves RWAs, tokens, PayFi, the Marketplace and the identity system across multiple domains, compliance and risk management are foundational to long-term development. NCC's compliance framework centers on entity layering, asset isolation, information disclosure, regional adaptation and risk control. ## Compliance Structure The Foundation provides ecosystem governance and long-term coordination. The Operating Entity is responsible for product development and operational execution. SPV structures handle RWA-asset management and legal isolation. Through this layered structure, NCC separates responsibilities across assets, operations, governance and applications. Supporting global expansion and risk isolation. ## Key Risk Factors The principal risks NCC faces include: Regulatory changes affecting RWAs, PayFi, token and other business modules. Underlying asset price volatility, default risk or cash-flow changes. Liquidity shortages or unstable depth causing trading friction. Smart-contract vulnerabilities and cross-chain system risk. Oracle data anomalies or interruption of external data sources. Pace of merchant expansion and shifts in market cycles. NCC mitigates these risks through legal structures, auditing, asset custody, risk parameters, liquidity management, multi-signature governance and continuous monitoring. Risk management is not a single module. It is a systemic capability running through asset onboarding, liquidity, applications and governance. In RWA scenarios, compliance and risk control determine not only platform safety, but also whether assets are accepted by institutions and broader users. NCC therefore manages asset onboarding, information disclosure, data synchronization, custody structures and yield distribution within a single risk framework. Avoiding information gaps between the asset side and the on-chain side. For PayFi and Marketplace scenarios, NCC focuses on the authenticity of consumer rights, the controllability of user data and the sustainability of partner scenarios. Ecosystem expansion must rest on clear responsibility structures, transparent rules and traceable on-chain records. --- # 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/trust-security-and-compliance/compliance-risk-management.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.