133 lines
7.4 KiB
HTML
133 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 7 - 加固、演示和验收</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">D7</span><span>Day 7 View</span></a>
|
||
<div class="quick-links">
|
||
<a class="pill" href="./index.html">返回总览</a>
|
||
<a class="pill" href="../agent%20week%20plan/day_7_hardening_demo_acceptance.md">周计划原文</a>
|
||
<a class="pill" href="../agent%20week%20plan/day_7_hardening_demo_acceptance.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" href="./day-6.html">Day 6</a>
|
||
<a class="pill active" href="./day-7.html">Day 7</a>
|
||
</div>
|
||
|
||
<section class="hero">
|
||
<div class="hero-badge">Hardening</div>
|
||
<h1>Day 7 加固、演示和验收</h1>
|
||
<p>Day 7 不再追求新增大功能，而是把 Day 1 到 Day 6 的链路整理成“可演示、可验收、可继续接手”的状态。没有这一层收口，前面做出来的东西很容易停在“只有作者自己懂”的阶段。</p>
|
||
<div class="hero-meta">
|
||
<div class="meta-card"><div class="meta-label">上游依赖</div><div class="meta-value">Day 1 到 Day 6 的全部核心路径。</div></div>
|
||
<div class="meta-card"><div class="meta-label">当天输出</div><div class="meta-value">回归记录、权限边界、审计和 Trace 补齐、测试记录、演示脚本、交接说明。</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_7_hardening_demo_acceptance.md">day_7_hardening_demo_acceptance.md</a></div>
|
||
</section>
|
||
<section class="card tone-teal">
|
||
<h3>执行细则</h3>
|
||
<p>执行层拆成核心链路回归、权限和风险边界、审计和 Trace、前端体验修补、测试补齐、评测集、演示数据、演示脚本和文档收尾。</p>
|
||
<div class="card-links"><a class="link-chip" href="../agent%20week%20plan/day_7_hardening_demo_acceptance.md">agent week plan/day_7</a></div>
|
||
</section>
|
||
<section class="card tone-olive">
|
||
<h3>架构依据</h3>
|
||
<p>主要受整体 README、开发路线图、可观测性和评测集约束。Day 7 的本质是把所有边界和证据讲清楚。</p>
|
||
<div class="card-links">
|
||
<a class="link-chip" href="../agent%20plan/00_README.md">00</a>
|
||
<a class="link-chip" href="../agent%20plan/05_development_roadmap.md">05</a>
|
||
<a class="link-chip" href="../agent%20plan/09_observability_and_trace.md">09</a>
|
||
<a class="link-chip" href="../agent%20plan/10_evaluation_and_testset.md">10</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>先汇总 Day 1 到 Day 6 未完成项，冻结新增需求。</div>
|
||
<div class="timeline-step"><strong>Step 2</strong>回归核心链路：资产、规则、语义解析、Orchestrator、User Agent、Hermes、Trace、AuditLog。</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>disabled 能力不能被调用。</li>
|
||
</ul>
|
||
</section>
|
||
<section class="card">
|
||
<h3>审计与 Trace</h3>
|
||
<ul class="list">
|
||
<li>规则保存、审核、上线都能看到 AuditLog。</li>
|
||
<li>Hermes 生成知识候选 / 规则草稿有审计。</li>
|
||
<li>任意演示路径都能追到 <code>run_id</code>。</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>从任务规则中心、规则详情、版本切换、上线拦截，到 User Agent 问答、Hermes 任务、Trace 和审计，都有明确步骤。</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">从规则中心到 User Agent，再到 Hermes 和 Trace，至少有一条完整演示路径可复现。</div></div>
|
||
<div class="row"><div class="row-label">证据完整</div><div class="row-value">AgentRun、ToolCall、AuditLog、测试记录、评测结果和演示脚本都存在。</div></div>
|
||
<div class="row"><div class="row-label">风险边界</div><div class="row-value">MVP 期间不存在绕过人工审核、自动付款、自动上线的暗门路径。</div></div>
|
||
<div class="row"><div class="row-label">可交接性</div><div class="row-value">下一位开发或 Codex 打开文档就能知道已完成、未完成和生产化前必补项。</div></div>
|
||
</div>
|
||
|
||
<div class="section-kicker">Common Misses</div>
|
||
<h2 class="section-title">这一天最容易漏掉的点</h2>
|
||
<ul class="list">
|
||
<li>只验证 Happy Path，不回归错误态、空态、禁用态和被权限拦截路径。</li>
|
||
<li>能讲演示，但没有测试记录和已知风险说明，交接质量会很差。</li>
|
||
<li>前 6 天的 TODO 没回写完成状态，导致页面和 Markdown 脱节。</li>
|
||
</ul>
|
||
|
||
<div class="footer">Day 7 的目标不是继续堆功能，而是把一周产出变成别人也能运行、理解和接手的系统。</div>
|
||
</div>
|
||
</body>
|
||
</html>
|