> 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/plans.md).
# 未来计划与风险观察
计划回答“接下来准备做什么”，风险信号回答“什么变化需要我重新考虑”。两者可以在对话中查询、准备和讨论。
定投系列、未来期次和 Nora 的计划查询结果。已完成与未来安排分别显示。
## 三种内容
| 内容 | 适合做什么 |
| ---- | ---------------------- |
| 单笔计划 | 安排某个未来日期的一笔买入或卖出 |
| 有限定投 | 按每周、每两周或每月生成一段有结束日期的安排 |
| 风险信号 | 保存具体关注问题，复查判断与历次变化 |
## 对话怎样连接它们
“后面有哪些安排？”会读取当前计划；“从下个月起，每周安排两百元，持续三个月”是准备新定投。想暂时停下，可以要求暂停对应系列，再按需要恢复。
也可以先让 Nora 更新一个关注中的风险问题，再结合新结果讨论未来安排。读取旧判断与更新判断是不同动作；创建计划仍按实际确认结果推进。
计划不提前冻结现金，也不代表交易已经发生。到期登记、净值等待、暂停与跳过都有明确状态。复查周期描述判断的新鲜度，不等于保证定时推送。
## 场景与细节
[用对话安排后续定投](/ray_evolv-docs/scenes/scene-plan.md) · [创建计划与定投](/ray_evolv-docs/systems/plans/schedule.md) · [到期、暂停与待核对](/ray_evolv-docs/systems/plans/due.md) · [风险信号](/ray_evolv-docs/systems/plans/signals.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/plans.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.
