> 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/xi-tong-zong-shu/2.-ji-suan-kong-zhi-mo-xing.md).
# 2. 计算控制模型
ComBoox公司股权及治理文件簿记系统（“**系统**”）采用“**有限状态机**”模型，模拟、控制股权交易及公司治理行为，具体来说：
2.1 状态
将股东名册、会议纪要等信息簿记在每一时刻所记录的信息内容视为其不同的**状态**，用各类**登记簿合约**来分别记录。
2.2 转变过程
将股权转让、股东会表决等股权交易活动或公司治理行为视为信息簿记在不同**状态**之间的**转变过程**，用**管理人合约**来详细的定义并控制其行为主体、行动步骤、行权条件和行为结果。
2.3 条件与流程
将公司章程等组织法类文件中规定的表决规则、提名规则等公司治理规则，以及优先权、随售权、反稀释等股权交易规则，视为信息簿记状态转换过程中所需遵循的**规则、条件和流程**，用**股东协议合约**来定义各项规则的**属性值、期限值**或**条件判断阈值**，随时反馈**管理人合约**在自动执行过程中的查询请求。
2.4 写指令脚本
将投资协议视为促使股权簿记状态发生转变的一系列写操作指令所构成的**批处理程序**或**脚本**，将其中约定的标的股权、当事方、数量、价格等交易要素视为写指令的输入参数，用**投资协议合约**来定义，使之可在**管理人合约**的控制下自动执行。
---
# 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/xi-tong-zong-shu/2.-ji-suan-kong-zhi-mo-xing.md?ask=&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.