> 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-trades.md).
# 把交易文字或截图交给 Nora
已有账单、交易文字或截图时，可以先让 Nora 整理，不必自己从空表开始逐笔填入。
> “把这些截图里的有效交易整理出来，已撤销的排除，再查查有没有记过的。先给我核对。”
对话请求与自动打开的批量核对窗口。图中仍有基金未就绪，属于待核对状态，不是全部保存成功。
{% stepper %}
{% step %}
### 提供材料
在会话中添加或粘贴图片，也可以提供交易文字。希望读取当前桌面上的交易图时，明确提出，并按对应视觉权限处理。
{% endstep %}
{% step %}
### 让 Nora 整理候选
检查基金、类型、日期、金额和份额。模型识别和查询能够减少重复输入，但原账单仍是核对依据。
{% endstep %}
{% step %}
### 补充与确认
单笔草稿可在会话里继续修正。批量记录进入核对窗口后，逐行校正、移除不需要的记录，选择归属账户和需要的资金池，再保存。
{% endstep %}
{% step %}
### 看到账本变化
核对已保存交易、关联资金流水和持仓。部分成功时先找回成功行，避免整批重复提交。
{% endstep %}
{% endstepper %}
## 下一次可以继续这样说
“最近记了哪几笔？”用于查询；“这笔金额改成……”若针对当前待确认草稿，可以沿原草稿修正。已正式入账的记录按页面提供的编辑方式处理。
[交易与资金的关系](/ray_evolv-docs/systems/ledger.md) · [单笔字段](/ray_evolv-docs/systems/ledger/first-buy.md) · [批量保存细节](/ray_evolv-docs/systems/ledger/batch.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-trades.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.
