> For the complete documentation index, see [llms.txt](https://comboox.gitbook.io/whitepaper-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://comboox.gitbook.io/whitepaper-en/technical-brochure/identity-and-verification.md).

# Identity and Verification

The smooth operation of the **system** and the realization of functions, depend on the authority control and the routing control of the writing instructions. In other words, for the calling instructions ("**writing instructions**") which can change the state of each smart contract, it is necessary to review and verify the identity and authority of the account that issued the instructions, and at the same time, it is necessary to strict control the target contract address and API referred by the writing instructions. When the writing instructions are strictly controls from the "receiving” and “sending" direction, the information of the whole system can be updated as the established commercial and legal logic.

The writing instructions in the system can be divided into three categories:

1. **System Configuration**: the drafting and system configuration actions triggered by external accounts, and will not directly lead to legal consequences;
2. **Legal Behavior**: the share transactions and corporate governance activities triggered by external accounts, and will not lead to direct legal consequences; and
3. **Algorithmic Control**: the actions triggered by the first two types of writing instructions, in which the **bookkeeper contract** may issue the writing instructions in orderly manner to change the **Register Contract**, **shareholders agreement**, **investment agreement**, and other smart contracts.

For the above three types of **writing instructions**, the system adopts three verification methods to control the access varying from the behaviors and scope of influence.

{% content-ref url="/pages/zdx39lpCmSktKVUGg0BR" %}
[Role and RolesRepo](/whitepaper-en/technical-brochure/identity-and-verification/role-and-rolesrepo.md)
{% endcontent-ref %}

{% content-ref url="/pages/Yt1OmKn8iBpAU8FJqLNf" %}
[Access Control Contract](/whitepaper-en/technical-brochure/identity-and-verification/access-control-contract.md)
{% endcontent-ref %}

{% content-ref url="/pages/S1EECdFWTm6Dw5Oeun9W" %}
[User and UsersRepo](/whitepaper-en/technical-brochure/identity-and-verification/user-and-usersrepo.md)
{% endcontent-ref %}


---

# 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://comboox.gitbook.io/whitepaper-en/technical-brochure/identity-and-verification.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.