134 lines
7.4 KiB
HTML
134 lines
7.4 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="zh-CN">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<title>Day 5 - User Agent MVP</title>
|
||
<link rel="stylesheet" href="./styles.css">
|
||
</head>
|
||
<body>
|
||
<div class="shell">
|
||
<div class="topbar">
|
||
<a class="brand" href="./index.html"><span class="brand-mark">D5</span><span>Day 5 View</span></a>
|
||
<div class="quick-links">
|
||
<a class="pill" href="./index.html">返回总览</a>
|
||
<a class="pill" href="../agent%20week%20plan/day_5_user_agent_mvp.md">周计划原文</a>
|
||
<a class="pill" href="../agent%20plan/weekly_execution_details/day_5_user_agent_mvp.md">执行细则原文</a>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="day-nav">
|
||
<a class="pill" href="./day-1.html">Day 1</a>
|
||
<a class="pill" href="./day-2.html">Day 2</a>
|
||
<a class="pill" href="./day-3.html">Day 3</a>
|
||
<a class="pill" href="./day-4.html">Day 4</a>
|
||
<a class="pill active" href="./day-5.html">Day 5</a>
|
||
<a class="pill" href="./day-6.html">Day 6</a>
|
||
<a class="pill" href="./day-7.html">Day 7</a>
|
||
</div>
|
||
|
||
<section class="hero">
|
||
<div class="hero-badge">User Agent</div>
|
||
<h1>Day 5 User Agent MVP</h1>
|
||
<p>这一天开始让“用户真的能问问题”。但 User Agent 只负责查询、解释、规则引用和草稿生成，绝不绕过权限做审批、付款、上线这类高风险动作。</p>
|
||
<div class="hero-meta">
|
||
<div class="meta-card"><div class="meta-label">上游依赖</div><div class="meta-value">Day 4 Orchestrator、Day 3 语义结构、Day 1 业务数据与日志模型、Day 2 规则资产。</div></div>
|
||
<div class="meta-card"><div class="meta-label">下游交接</div><div class="meta-value">Day 7 要拿它做问答演示、规则解释演示和草稿生成演示。</div></div>
|
||
<div class="meta-card"><div class="meta-label">当天关键</div><div class="meta-value">回答可读、引用可追溯、草稿可确认、高风险不自动执行。</div></div>
|
||
</div>
|
||
</section>
|
||
|
||
<div class="section-kicker">Three-Layer Mapping</div>
|
||
<h2 class="section-title">三层文档映射</h2>
|
||
<div class="grid three">
|
||
<section class="card tone-warm">
|
||
<h3>路线图</h3>
|
||
<p>周计划要求做用户自然语言入口、报销 / 应收 / 应付查询解释、规则引用解释、建议草稿和前端入口。</p>
|
||
<div class="card-links"><a class="link-chip" href="../agent%20week%20plan/day_5_user_agent_mvp.md">day_5_user_agent_mvp.md</a></div>
|
||
</section>
|
||
<section class="card tone-teal">
|
||
<h3>执行细则</h3>
|
||
<p>执行层拆成输入输出、查询处理、规则解释、风险解释、草稿生成、知识库读取骨架、对话入口、安全边界和测试。</p>
|
||
<div class="card-links"><a class="link-chip" href="../agent%20plan/weekly_execution_details/day_5_user_agent_mvp.md">weekly_execution_details/day_5</a></div>
|
||
</section>
|
||
<section class="card tone-olive">
|
||
<h3>架构依据</h3>
|
||
<p>主要受 Agent 职责划分、运行时流程、知识架构和规则形成生命周期约束。所有高风险动作只能停留在建议或草稿层。</p>
|
||
<div class="card-links">
|
||
<a class="link-chip" href="../agent%20plan/03_agent_responsibilities.md">03</a>
|
||
<a class="link-chip" href="../agent%20plan/04_orchestrator_and_runtime_flow.md">04</a>
|
||
<a class="link-chip" href="../agent%20plan/12_llm_wiki_knowledge_architecture.md">12</a>
|
||
<a class="link-chip" href="../agent%20plan/13_rule_formation_lifecycle.md">13</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
|
||
<div class="section-kicker">Build Order</div>
|
||
<h2 class="section-title">推荐开发顺序</h2>
|
||
<div class="timeline">
|
||
<div class="timeline-step"><strong>Step 1</strong>先定 <code>UserAgentRequest</code> / <code>UserAgentResponse</code> 协议。</div>
|
||
<div class="timeline-step"><strong>Step 2</strong>优先实现报销、应收、应付查询处理器。</div>
|
||
<div class="timeline-step"><strong>Step 3</strong>补规则解释和风险解释，让回答有依据而不是只给一句话。</div>
|
||
<div class="timeline-step"><strong>Step 4</strong>补草稿生成与知识读取骨架。</div>
|
||
<div class="timeline-step"><strong>Step 5</strong>最后接前端问答入口、加载态、错误态和确认提示。</div>
|
||
</div>
|
||
|
||
<div class="section-kicker">Must Deliver</div>
|
||
<h2 class="section-title">今天必须产出的东西</h2>
|
||
<div class="grid two">
|
||
<section class="card">
|
||
<h3>三类财务查询</h3>
|
||
<ul class="list">
|
||
<li>报销查询可读，能查金额、状态或进度。</li>
|
||
<li>应收查询可读，能查客户未收金额或账龄。</li>
|
||
<li>应付查询可读，能查供应商待付款或付款状态。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>解释能力</h3>
|
||
<ul class="list">
|
||
<li>规则解释能引用 active 规则、版本号和更新时间。</li>
|
||
<li>风险解释能说明风险类型、原因和建议动作。</li>
|
||
<li>知识库不可用时要优雅降级。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>草稿而非执行</h3>
|
||
<ul class="list">
|
||
<li>可生成报销处理意见草稿、应收催收建议草稿、应付付款建议草稿。</li>
|
||
<li>草稿必须写明“待人工确认”。</li>
|
||
<li>草稿行为写入审计日志和 AgentRun 结果。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>用户入口</h3>
|
||
<ul class="list">
|
||
<li>前端输入框走 Orchestrator，不绕行。</li>
|
||
<li>显示回答、引用、建议动作、确认提示和 <code>run_id</code>。</li>
|
||
<li>有加载态和错误态。</li>
|
||
</ul>
|
||
</section>
|
||
</div>
|
||
|
||
<div class="section-kicker">Acceptance Snapshot</div>
|
||
<h2 class="section-title">验收快照</h2>
|
||
<div class="table-like">
|
||
<div class="row"><div class="row-label">问答闭环</div><div class="row-value">用户在页面上能完成一次自然语言提问、拿到回答、看到引用和 run_id。</div></div>
|
||
<div class="row"><div class="row-label">三类场景</div><div class="row-value">至少报销、应收、应付三类财务问题都有结构化回答。</div></div>
|
||
<div class="row"><div class="row-label">引用能力</div><div class="row-value">“为什么这笔报销有风险”这类问题能引用规则，而不是只给模糊判断。</div></div>
|
||
<div class="row"><div class="row-label">安全边界</div><div class="row-value">“直接付款”“直接审批”类提示不会自动执行，只能变成建议或草稿。</div></div>
|
||
</div>
|
||
|
||
<div class="section-kicker">Common Misses</div>
|
||
<h2 class="section-title">这一天最容易漏掉的点</h2>
|
||
<ul class="list">
|
||
<li>只返回原始查询数据，不把结果翻译成用户可读回答。</li>
|
||
<li>只做草稿内容，不做 <code>requires_confirmation</code> 和审计日志。</li>
|
||
<li>绕过 Orchestrator 直接从前端打 User Agent，导致 Day 4 的统一链路失效。</li>
|
||
</ul>
|
||
|
||
<div class="footer">Day 5 的判断标准是：用户能问、系统能答、回答有依据、动作不越权。</div>
|
||
</div>
|
||
</body>
|
||
</html>
|