> For the complete documentation index, see [llms.txt](https://blockchain1.gitbook.io/cac_classic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blockchain1.gitbook.io/cac_classic/cacclasssic-jian-jie.md).
# CAC\_Classsic 简介
**全球首个实现“现实资产 × 全链执行 × 自动收益分配”
的去中心化商业文明系统**
\
由CAC基金会与CAC DAO联合打造，CAC构建了一个以RWA为底层驱动力的全链生态，涵盖DeFi、GameFi、SocialFi、NFT等核心板块。
在这里，资产映射、合约执行、收益分配、社区治理全部链上完成，真正实现“无中介、可验证、可持续”的新型经济体系。
**CAC，让区块链重回信任的原点，开启价值互联网的新时代**
---
# 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://blockchain1.gitbook.io/cac_classic/cacclasssic-jian-jie.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.