> 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-plan.md).
# 用对话安排后续定投
当你已经想好投入对象、节奏和期限，可以直接告诉 Nora，先看到未来安排，再决定是否确认。
> “从下个月开始，每周安排两百元，持续三个月，用刚才选好的账户和资金池。基金我来确认。”
{% stepper %}
{% step %}
### 说清安排
给出基金、账户或资金来源、每期金额、频率和起止范围。存在多个合理资金池时，选择本次使用的一个。
{% endstep %}
{% step %}
### 检查生成的草稿
核对基金代码、金额、费率及日期。你可以先问清规则，再确认创建；不要把讨论一个计划理解为已经成交。
{% endstep %}
{% step %}
### 随时查询或暂停
创建后问“后面有哪些安排”。需要暂停时指明对应定投；恢复后查看未来期次，不假定自动补回暂停期间错过的投入。
{% endstep %}
{% step %}
### 到期后核对记录
查看等待执行、已登记或待核对的说明。已经登记的事项不要再手工录一笔相同交易。
{% endstep %}
{% endstepper %}
定投卡保留每期金额、剩余次数和完成状态；Nora 可以读取相应安排。
## 把风险观察带进讨论
你也可以要求更新一个已关注的风险信号，再结合新判断讨论计划。建议复查周期表示判断的新鲜度，不是承诺自动按期推送。
[计划体系](/ray_evolv-docs/systems/plans.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/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-plan.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.
