> For the complete documentation index, see [llms.txt](https://docs.zongsoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zongsoft.com/overview.md).

# 概览

- [什么是 Zongsoft](https://docs.zongsoft.com/overview/what-is-zongsoft.md): 了解 Zongsoft 开源框架系列的组成、定位与适用场景。
- [设计理念](https://docs.zongsoft.com/overview/conception.md): 理解 Zongsoft 对公共契约、插件装配、显式元数据和部署组合的设计取舍。
- [架构总览](https://docs.zongsoft.com/overview/architecture.md): 从依赖方向和运行流程理解 核心类库、插件、宿主与基础设施的职责。
- [基础概念与协作方式](https://docs.zongsoft.com/overview/concepts.md): 区分宿主、插件、模块、服务、提供者、构件和四类元数据文件。
- [插件化](https://docs.zongsoft.com/overview/pluginization.md): Zongsoft 插件化应用的基本概念和运行方式。
- [为什么需要插件化](https://docs.zongsoft.com/overview/pluginization/why-pluginization.md): 从复杂 SaaS 的支付、交易与设备协作出发，理解巨石应用的维护困境，以及分层、业务分块和插件装配带来的变化。
- [从业务变化确定模块边界](https://docs.zongsoft.com/overview/pluginization/business-boundaries.md): 先找业务变化，再划分模块：规则、装配、编译与交付各回答不同的问题。
- [让业务能力跨宿主复用](https://docs.zongsoft.com/overview/pluginization/host-independent-business.md): 把业务动作留在服务里，让控制器、命令和后台入口共用同一套规则。
- [把扩展点设计成协作契约](https://docs.zongsoft.com/overview/pluginization/extension-contracts.md): 扩展点由装配路径与行为约定共同构成，为过滤器、验证器和事件定义可维护的协作契约。
- [从局部改造到可验证的插件交付](https://docs.zongsoft.com/overview/pluginization/evolutionary-delivery.md): 用可独立验收的业务切口渐进引入插件，让每一步都可运行、可观察、可回退。
- [部署模型](https://docs.zongsoft.com/overview/deployment.md): 了解 Zongsoft 中部署、打包和升级的整体模型。


---

# 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://docs.zongsoft.com/overview.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.