> For the complete documentation index, see [llms.txt](https://comboox.gitbook.io/whitepaper-cn/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-cn/cao-zuo-zhi-nan/ti-ming-dong-shi-bing-qu-de-xi-wei.md).

# 提名董事并取得席位

## 提名董事并取得席位 

根据股东协议拥有提名权的股东，可以通过ComBoox系统提名董事候选人，经由股东会表决通过后，候选人即可就任董事。

{% embed url="<https://youtu.be/Jg25kTt86zY>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://comboox.gitbook.io/whitepaper-cn/cao-zuo-zhi-nan/ti-ming-dong-shi-bing-qu-de-xi-wei.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.