> 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.md).
# 整体结构与功能体系
Evolv 的页面各有职责，对话把这些能力串在一起。先理解整体结构，再选择要深入了解的一部分。
```mermaid
flowchart TB
U[你提出目标] --> N[Nora 理解、查询与组织操作]
N --> I[投资管理：资金、交易、持仓与计划]
N --> R[研究：基金、持仓和自定义问题]
I -->|按研究需要提供业务背景| R
K[知识：带来源、时间和条件的认识] -->|已有认识参与| R
R --> B[报告：本次研究的表达与依据]
R -->|合格公共认识积累| K
K -->|供后续讨论查阅| N
B -->|共读、解释和追问| N
```
## 各部分的独立价值
投资管理本身就是完整功能，不只是研究的原材料。知识也不等于报告文件夹：报告保留某一次研究，知识保留可以在其他问题中复用的认识。
## 两种使用方式相互配合
你可以先对话，再看结果；也可以先打开一份报告或一只基金，再围绕当前对象提问。查询可以直接返回；涉及写入时按该操作的确认方式完成；研究遵循需求和大纲设置。不是每句话都要确认，也不是每项功能都必须先打开表单。
[场景体验与教程](/ray_evolv-docs/scenes.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.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.