> For the complete documentation index, see [llms.txt](https://ray-evolv.gitbook.io/ray_evolv-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ray-evolv.gitbook.io/ray_evolv-docs/systems/knowledge.md).
# 知识积累与复用体系
有用的认识不必随着一次聊天或报告结束而散失。Evolv 将可以复用的内容连同来源、时间和适用条件保留，供下一次查找、讨论与研究使用。
知识按基金档案与宏观主题组织；每项认识可以进一步查看来源与历史。
## 什么会成为知识
研究过程中形成的合格公共认识可以积累下来；你也可以明确请 Nora 把当前讨论整理为知识候选，再核对确认。材料有来源、主体明确且适合保留，比单纯保存一大段文字更重要。
## 怎样组织与查找
基金档案把同一基金的认识放在一起；宏观与市场按主题组织；模块聚合同一方面的内容；具体知识保留当前认识、历史状态及来源。你可以通过页面搜索，也可以直接问 Nora。
## 怎样看见复用
下一次提出相关问题时，查看回答采用的材料与来源，确认先前保存的认识是否参与。时间和条件也应一起带入；需要新资料时继续补充，而不是把旧结论原样套用。
公共知识描述的是内容性质，不表示上传到公共网站。个人持仓属于业务记录；“以后先说结论”属于个人偏好，二者有各自的保存方式。
[保存认识并在下次用上](/ray_evolv-docs/scenes/scene-knowledge.md) · [查找与历史](/ray_evolv-docs/systems/knowledge/find.md) · [知识候选](/ray_evolv-docs/systems/knowledge/capture.md) · [复用与纠正](/ray_evolv-docs/systems/knowledge/reuse.md)
***
返回[整体结构与功能体系](/ray_evolv-docs/systems.md) · [认识 Evolv](/ray_evolv-docs/home.md)
---
# 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://ray-evolv.gitbook.io/ray_evolv-docs/systems/knowledge.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.
