> 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-research.md).
# 从一个问题到一份报告
研究可以从一句明确的问题开始，后续通过对话补充重点和调整大纲。你负责目标，Nora 帮你把研究组织起来。
> “研究一下数据中心能效变化为什么不一定让电费下降，重点看成立条件，不展开个股推荐。”
{% stepper %}
{% step %}
### 提出问题并确认启动
可以研究一只基金、当前持仓或自定义问题。Nora 按实际入口准备启动确认，创建成功后沿同一任务继续。
{% endstep %}
{% step %}
### 明确需求
说明用途、范围、重点或不要展开的部分。已有信息不必重说；关键差异在这一步确认。
{% endstep %}
{% step %}
### 讨论大纲
先查看组织方式，再说“增加电价与负载的影响”“这部分不要展开”。核对修订后的内容，按设置确认后继续。
{% endstep %}
{% step %}
### 看进度与结果
研究工作台展示阶段和已完成内容。可以询问当前进度，完成后打开报告；符合条件的失败任务可从保存点恢复。
{% endstep %}
{% endstepper %}
待批大纲与 Nora 的解释同屏；可以先理解方案，再决定是否继续。
## 三类研究怎样选
基金研究聚焦产品本身；持仓分析利用相关业务背景；自定义研究围绕你提出的问题。共同流程相同，看到的资料范围不同。
报告出来之后，继续[一起阅读与追问](/ray_evolv-docs/scenes/scene-reading.md)。需要停止或提交疑难材料时，使用研究页对应入口；不要把工具中未开放的动作写成对话已经执行。
[研究体系](/ray_evolv-docs/systems/research.md) · [三类入口](/ray_evolv-docs/systems/research/research-start.md) · [审批设置](/ray_evolv-docs/systems/research/outline.md) · [进度与恢复](/ray_evolv-docs/systems/research/progress.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-research.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.
