134 lines
7.5 KiB
HTML
134 lines
7.5 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 6 - Hermes 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">D6</span><span>Day 6 View</span></a>
|
||
<div class="quick-links">
|
||
<a class="pill" href="./index.html">返回总览</a>
|
||
<a class="pill" href="../agent%20week%20plan/day_6_hermes_mvp.md">周计划原文</a>
|
||
<a class="pill" href="../agent%20plan/weekly_execution_details/day_6_hermes_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" href="./day-5.html">Day 5</a>
|
||
<a class="pill active" 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">Hermes</div>
|
||
<h1>Day 6 Hermes MVP</h1>
|
||
<p>Hermes 是后台数字员工，不做即时对话，而是负责定时巡检、风险预警、日报统计、知识候选和规则草稿。它的关键不是“会不会说”，而是“任务能不能跑、结果能不能追”。</p>
|
||
<div class="hero-meta">
|
||
<div class="meta-card"><div class="meta-label">上游依赖</div><div class="meta-value">Day 4 的 Orchestrator 路由，Day 1 的任务与日志表，Day 3 的语义结构，Day 5 可复用的风险/规则/知识接口。</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">任务入口、风险项结构、OCR Mock、知识候选和规则草稿都必须可追溯。</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>周计划要求实现 Hermes 调度入口、每日风险巡检、统计任务、知识库维护、OCR Mock 和运行结果面板或 API。</p>
|
||
<div class="card-links"><a class="link-chip" href="../agent%20week%20plan/day_6_hermes_mvp.md">day_6_hermes_mvp.md</a></div>
|
||
</section>
|
||
<section class="card tone-teal">
|
||
<h3>执行细则</h3>
|
||
<p>执行层拆成输入输出、任务调度入口、风险巡检、每日统计、OCR 接入点、知识库维护、规则草稿形成、结果展示和测试。</p>
|
||
<div class="card-links"><a class="link-chip" href="../agent%20plan/weekly_execution_details/day_6_hermes_mvp.md">weekly_execution_details/day_6</a></div>
|
||
</section>
|
||
<section class="card tone-olive">
|
||
<h3>架构依据</h3>
|
||
<p>主要受 Agent 职责、OCR 架构、知识库架构和反馈学习闭环约束。Hermes 能生成候选和草稿，但不能自动发布正式结果。</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/11_ocr_invoice_architecture.md">11</a>
|
||
<a class="link-chip" href="../agent%20plan/12_llm_wiki_knowledge_architecture.md">12</a>
|
||
<a class="link-chip" href="../agent%20plan/15_feedback_learning_loop.md">15</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>HermesTaskRequest</code> / <code>HermesTaskResult</code>。</div>
|
||
<div class="timeline-step"><strong>Step 2</strong>建立手动触发任务 API，经 Orchestrator 路由到 Hermes。</div>
|
||
<div class="timeline-step"><strong>Step 3</strong>补风险巡检和每日统计的结构化输出。</div>
|
||
<div class="timeline-step"><strong>Step 4</strong>接入 OCR Mock、知识候选生成、规则草稿生成。</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>任务经 Orchestrator 进入 Hermes。</li>
|
||
<li>结束后能更新最近执行时间和状态。</li>
|
||
</ul>
|
||
</section>
|
||
<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>知识候选默认是 <code>draft</code>，不能自动发布。</li>
|
||
<li>规则草稿保存为 <code>asset_type=rule</code>，状态为 <code>draft</code>。</li>
|
||
<li>两类生成都要写审计日志。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>OCR Mock 与结果展示</h3>
|
||
<ul class="list">
|
||
<li>OCR 服务接口和输入输出结构定下来。</li>
|
||
<li>当前阶段允许完全使用 Mock 结果。</li>
|
||
<li>任务详情或运行日志中能直接看到 Hermes 的执行结果。</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">至少一个任务可以手动触发，并能查到结构化结果。</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">知识候选和规则草稿都能生成，但都不是 active / published 正式状态。</div></div>
|
||
<div class="row"><div class="row-label">可观察性</div><div class="row-value">不用查数据库，也能从任务详情或运行日志判断 Hermes 是否执行成功。</div></div>
|
||
</div>
|
||
|
||
<div class="section-kicker">Common Misses</div>
|
||
<h2 class="section-title">这一天最容易漏掉的点</h2>
|
||
<ul class="list">
|
||
<li>只做 Hermes 服务逻辑，不做任务入口和结果展示，最后无法演示。</li>
|
||
<li>能生成知识或规则，但没把状态锁在 <code>draft</code>，会直接越过人工审核边界。</li>
|
||
<li>OCR Mock 只返回一段自由文本，不定义结构字段，后面无法和规则或风险逻辑对接。</li>
|
||
</ul>
|
||
|
||
<div class="footer">Day 6 的价值是让“后台数字员工”第一次具备可触发、可解释、可留痕的闭环。</div>
|
||
</div>
|
||
</body>
|
||
</html>
|