How an Agent Client Presents Research and Citations
An article on ETF Agent client architecture explains how an Agent client should map user actions, concurrent runs, real-time events, historical reads, and citations. It emphasizes that receiving an SSE string does not prove that a research result was rendered correctly. Proposed acceptance scenarios cover misrouted responses, stale revisions, premature saves, permission errors, and citations linked to the wrong version. The article also points to Open ETF Agent’s local example for reading saved reports and sources, but states that the example was not rerun during its preparation and that it is not a complete product client.
The article distinguishes SSE transport from application-level handling of content identity, permissions, revision merging, and version-bound citations. These constraints are central to ensuring that users see and operate on the intended task, version, and currently accessible material.
用户提交一项基金比较，页面开始出现文字。他又问了一个术语问题，随后刷新页面，回来时打开一条引用，最后决定停止仍在进行的比较。
单独看，每一步都很普通。放在同一条交互链上，问题才显现出来：后到的回答应该落在哪条问题下面？刷新读回的内容能否覆盖刚刚看到的新版本？点击停止之后，页面应该显示“正在停止”，还是直接宣布“已停止”？
Agent 客户端的核心工作，是把用户操作、任务进展和研究结果稳定地对应起来。 SSE 只是其中一种实时传输方式。浏览器接到了字符串，并不意味着它已经正确呈现了一次研究。
在 ETF Agent 的职责划分中，客户端负责交互与阅读。本文以既有客户端机制和公开工程记录为例，解释这项职责；文中的验收场景是设计检查方法，不是本次重新执行的测试报告。完整产品客户端与独立的 Open ETF Agent 教学实现也不是同一套交付范围。