> 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/scenes/scene-knowledge.md).
# 保存认识并在下次用上
讨论中得到一条值得保留的认识时，不必另建一套笔记目录。可以让 Nora 整理候选，带着来源与条件留下来。
> “把刚才关于这个问题的公开资料整理为知识候选，保留时间、适用条件和来源。”
{% stepper %}
{% step %}
### 选出值得保留的内容
说明哪段讨论、哪份公开材料或哪个主体。个人账户余额和协作偏好分别属于业务与个人记忆，不混成公共知识。
{% endstep %}
{% step %}
### 核对候选
检查陈述、主体、定位、时间与来源。多个候选分别检查，确认要保留的内容。
{% endstep %}
{% step %}
### 确认并找回来
保存后到知识页搜索、打开具体认识，也可以让 Nora 读取。不能只凭一句“准备好了”判断入库完成。
{% endstep %}
{% step %}
### 在下一次问题中使用
换一种自然说法提出相关问题，查看实际采用的知识和来源。缺少新资料时再补充，不把旧结论机械套用。
{% endstep %}
{% endstepper %}
知识页提供按基金与主题查找、历史状态和具体条目的入口。
研究过程形成的合格公共认识也会积累下来。报告是一次研究的表达，知识则在后续讨论与研究中发挥作用；不是所有消息都自动长期保存。
[知识体系](/ray_evolv-docs/systems/knowledge.md) · [候选确认](/ray_evolv-docs/systems/knowledge/capture.md) · [来源与历史](/ray_evolv-docs/systems/knowledge/find.md)
***
返回[场景体验与教程](/ray_evolv-docs/scenes.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/scenes/scene-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.
