> 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/research.md).
# 研究与报告体系
从你真正想回答的问题出发，确定范围和大纲，利用已有知识、补充缺少的资料，形成可以阅读和继续追问的报告。
研究有基金、持仓和自定义三种入口，后续共享研究与报告流程。
## 三种起点
| 入口 | 研究什么 | 需要什么背景 |
| ----- | ----------------- | ---------------- |
| 基金研究 | 一只基金本身的特征、表现和适用条件 | 确认基金身份及你的关注重点 |
| 持仓分析 | 当前组合与安排 | 相关持仓、交易、资金、计划和信号 |
| 自定义研究 | 你提出的专题问题 | 主体、范围、用途与相关材料 |
## 一次研究怎样展开
```mermaid
flowchart LR
A[提出问题] --> B[明确需求]
B --> C[查看或修改大纲]
C --> D[研究与取材]
D --> E[报告与证据]
E --> F[继续讨论与补充材料]
```
这条流程可以从 Nora 对话发起。你可以补充重点、修订大纲、查看进度，完成后让 Nora 打开报告。工作台展示当前阶段与保存结果。需求和大纲是否自动批准，分别由设置控制。
## 报告值得看什么
摘要帮助抓住主要回答；正文说明推理与条件；证据让你回到采用的材料；疑难保留尚未解决的问题。报告生成完成不等于所有问题都得到充分回答，条件性结论仍需要结合实际范围使用。
研究留下的合格公共认识可以进入[知识体系](/ray_evolv-docs/systems/knowledge.md)，后续研究优先寻找可复用部分。报告是这次研究的版本，知识则可以继续更新和再次使用。
## 场景与查阅入口
[从一个问题到一份报告](/ray_evolv-docs/scenes/scene-research.md) · [与 Nora 一起读报告](/ray_evolv-docs/scenes/scene-reading.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/systems/research/reports.md) · [补料与新版](/ray_evolv-docs/systems/research/materials.md) · [研究库](/ray_evolv-docs/systems/research/library.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/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.
