> 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/ncc-identity-layer.md).

# NCC Identity Layer

The NCC Identity Layer is the identity and access-permission infrastructure of the NCC ecosystem. It transforms users' on-chain behavior, application participation, consumer records, governance involvement and asset holdings into a composable identity and reputation layer.

## From Account to Identity

Traditional Web3 accounts typically represent only addresses and asset balances. The NCC Identity Layer goes further by tracking user behavior and permissions across the network. Carrying ecosystem tier, access eligibility, consumer benefits, task status, governance records and application permissions.

This means a user is no longer merely a wallet address, but a participant with identity, reputation and portable rights inside the NCC ecosystem.

## Ecosystem Value of the Identity Layer

For the Marketplace, the Identity Layer can recognize user access and rights status. For the PayFi network, it connects consumer behavior with on-chain rights. For governance, it supports more grounded community participation. For partners, it provides clearer user relationships and ecosystem-contribution identification.

The Identity Layer's value lies in converting scattered user activity into composable on-chain relationships. Records of asset holdings, application participation, consumer behavior, governance activity and ecosystem tasks become the basis for subsequent rights identification, application access and risk assessment.

While protecting user sovereignty, the NCC Identity Layer emphasizes verifiable, portable and selectively disclosable identity. Users should not be locked into any single platform. They should be able to carry their identity and rights across applications within the NCC ecosystem.


---

# 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/ncc-identity-layer.md?ask=<question>&goal=<endgoal>
```

`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.