> 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/ledger.md).
# 投资管理：账本与资金
把现金、交易和持仓放在同一本账里，才能回答“钱在哪里、怎样变化、现在持有什么”。
你可以直接问 Nora：“我现在有哪些待投资金？”也可以让它准备新账户、资金池、入金或交易。页面保留真实记录，方便回看和核对。
账户与资金池和 Nora 的查询结果同时展示；图片是既有记录的实机画面。
## 从账户到持仓
| 内容 | 负责什么 | 与其他内容的关系 |
| ----- | --------------- | ----------------- |
| 账户 | 区分平台与账本归属 | 资金池、交易和计划都选对账户 |
| 资金池 | 按用途组织现金 | 入金、出金、划拨及关联交易改变余额 |
| 交易 | 记录已经发生的买卖、分红和转换 | 形成持仓和成本，关联现金流水 |
| 持仓与收益 | 查看份额、成本、市值及变化 | 来源于交易与可用净值，注意数据日期 |
| 关注基金 | 保存感兴趣的对象 | 不等于已买入，不自动生成持仓 |
## 对话能帮你完成什么
从询问当前资金开始，接着要求新建账户和池，或把一笔实际交易整理成待确认卡。缺少可以查到的信息时先读取，确实需要你决定的内容再补问。你还可以继续修正当前草稿，不必把整件事重新说一遍。
账户和交易是本地记录，记账不会向银行或交易平台下单。创建未来安排则进入[计划体系](/ray_evolv-docs/systems/plans.md)，不提前当作成交。
## 先看完整场景
[一句话整理账户和资金](/ray_evolv-docs/scenes/scene-money.md) · [把交易文字或截图交给 Nora](/ray_evolv-docs/scenes/scene-trades.md)
## 按需查阅操作细节
[账户与资金池](/ray_evolv-docs/systems/ledger/accounts.md) · [第一笔买入](/ray_evolv-docs/systems/ledger/first-buy.md) · [卖出、分红与转换](/ray_evolv-docs/systems/ledger/other-trades.md) · [批量核对](/ray_evolv-docs/systems/ledger/batch.md) · [持仓和更正记录](/ray_evolv-docs/systems/ledger/holdings.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/ledger.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.
