> 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-reading.md).
# 与 Nora 一起读报告
报告不必读完再另开聊天。看到不理解的判断、图表或条件时，就在当前阅读位置提出问题。
{% stepper %}
{% step %}
### 打开要讨论的报告
先确认标题和版本。可以让 Nora 找回已有报告并打开，或从研究库进入。
{% endstep %}
{% step %}
### 指向具体内容
选中正文的一段话，将它作为本次讨论的引用内容。发送前查看右侧输入区上方的 **正在讨论这段**，确认引用的是你想问的文字，再输入问题。例如“详细解释”“这句话依据什么”“哪些条件变化会让结论不成立”。
也可以直接说明章节或图表。换一个问题时，留意旧引用是否仍保留；不需要时可点击引用框右侧的 × 移除。
{% endstep %}
{% step %}
### 继续追问
发送后出现“正在理解并处理你的问题”表示请求还在处理中，不是完整答案。等待回答出现，再围绕同一段继续问“为什么”“那意味着什么”。核对回答仍针对当前报告，而不是换成泛泛的常识解释。
{% endstep %}
{% step %}
### 展开来源
点击正文附近的 **查看证据**，对照实际材料，辨认来源披露、条件、推断与未回答部分。有新资料时可以通过对应疑难补料。
{% endstep %}
{% endstepper %}
证据检查器展开实际采用的材料与冻结摘录，可以与正文判断对照。
截图展示的是报告共读，选中文字后的具体交互也可按上述步骤操作。已封存报告有自己的日期和条件，不能把历史判断自动当成今天的事实。
[报告与证据说明](/ray_evolv-docs/systems/research/reports.md) · [补料与新版](/ray_evolv-docs/systems/research/materials.md) · [对话体系](/ray_evolv-docs/systems/nora.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-reading.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.
