document/development/agent_week_plan_html/index.html

<!DOCTYPE html>
<html lang="zh-CN">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Agent Week Plan HTML</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">A7</span>
        <span>Agent Week HTML</span>
      </a>
      <div class="quick-links">
        <a class="pill" href="../agent%20week%20plan/MASTER_TODO.md">周计划总控</a>
        <a class="pill" href="../agent%20week%20plan/00_README.md">周计划说明</a>
        <a class="pill" href="../agent%20plan/00_README.md">架构目录</a>
      </div>
    </div>

    <section class="hero">
      <div class="hero-badge">Static Map</div>
      <h1>把 7 天周计划变成可直接浏览的开发视图</h1>
      <p>这一套 HTML 页面不是替代 Markdown，而是把 <code>agent week plan</code> 和 <code>agent plan</code> 的对应关系收成一个稳定入口。每天的路线图和执行清单现在已经并到同一份 daily 文档里。</p>
      <div class="hero-meta">
        <div class="meta-card">
          <div class="meta-label">阅读顺序</div>
          <div class="meta-value">先总览，再选 Day，再跳转到具体 Markdown 落地执行。</div>
        </div>
        <div class="meta-card">
          <div class="meta-label">核心视图</div>
          <div class="meta-value">路线图、执行细则、架构依据三层同时可见。</div>
        </div>
        <div class="meta-card">
          <div class="meta-label">适用对象</div>
          <div class="meta-value">Codex 开发、后端开发、前端开发、项目 owner、验收人员。</div>
        </div>
      </div>
    </section>

    <div class="section-kicker">How To Use</div>
    <h2 class="section-title">怎么用这套页面</h2>
    <div class="grid two">
      <section class="card tone-teal">
        <h3>Codex 开发视角</h3>
        <ol class="list">
          <li>先看今天在哪一天，确认上游依赖和下游交接。</li>
          <li>用“两层映射”定位：daily 文档看目标和步骤，架构文档看约束。</li>
          <li>按“推荐开发顺序”推进，不跳天，不跨层乱做。</li>
          <li>完成后回到原始 Markdown，把 TODO、阻塞、交接更新回文档。</li>
        </ol>
      </section>
      <section class="card tone-warm">
        <h3>人工开发与验收视角</h3>
        <ol class="list">
          <li>先看每一天的“今日定位”，知道这一天到底产出什么。</li>
          <li>再看“今天必须产出的东西”和“验收快照”，确认完成标准。</li>
          <li>最后跳转到对应 Markdown，逐条执行或验收。</li>
          <li>如果发现跨天阻塞，优先回前一天补地基，而不是在当前天临时兜底。</li>
        </ol>
      </section>
    </div>

    <div class="section-kicker">Three Layers</div>
    <h2 class="section-title">文档结构一眼看清</h2>
    <div class="grid three">
      <section class="card">
        <h3>1. 周计划路线图</h3>
        <p>定义每天的大方向、交付物和验收门槛。用于排期、对齐和验收。核心入口是 <code>MASTER_TODO.md</code> 和 Day 1 到 Day 7 daily 文档。</p>
        <div class="card-links">
          <a class="link-chip" href="../agent%20week%20plan/00_README.md">00_README</a>
          <a class="link-chip" href="../agent%20week%20plan/MASTER_TODO.md">MASTER_TODO</a>
        </div>
      </section>
      <section class="card">
        <h3>2. 每日执行清单</h3>
        <p>每天的开发目标已经拆到对应 daily 文档中的详细执行清单，直接覆盖模型、字段、接口、服务、前端、测试和验收证据。</p>
        <div class="card-links">
          <a class="link-chip" href="../agent%20week%20plan/00_README.md">00_README</a>
          <a class="link-chip" href="../agent%20week%20plan/MASTER_TODO.md">MASTER_TODO</a>
        </div>
      </section>
      <section class="card">
        <h3>3. 架构依据</h3>
        <p>提供为什么要这么做、协议怎么定、权限和审计边界是什么。它不直接当 TODO，但所有实现都要受它约束。</p>
        <div class="card-links">
          <a class="link-chip" href="../agent%20plan/01_overall_architecture.md">总体架构</a>
          <a class="link-chip" href="../agent%20plan/02_semantic_ontology.md">语义本体</a>
          <a class="link-chip" href="../agent%20plan/09_observability_and_trace.md">观测与 Trace</a>
        </div>
      </section>
    </div>

    <div class="section-kicker">Seven Days</div>
    <h2 class="section-title">7 天总览</h2>
    <div class="grid two">
      <section class="card tone-olive">
        <h3>Day 1 基础模型与工程骨架</h3>
        <p><strong>当前状态：</strong>已完成（2026-05-11）。先把 Agent 资产、版本、审核、运行日志、审计日志，以及报销 / 应收 / 应付的最小业务数据来源定下来。后面所有能力都站在这一天的模型上。</p>
        <div class="card-links">
          <a class="link-chip" href="./day-1.html">打开日视图</a>
          <a class="link-chip" href="../agent%20week%20plan/day_1_foundation_models.md">周计划</a>
          <a class="link-chip" href="../agent%20week%20plan/day_1_foundation_models.md">合并文档</a>
        </div>
      </section>
      <section class="card tone-teal">
        <h3>Day 2 任务规则中心联调</h3>
        <p>把规则、技能、MCP、任务从静态 UI 拉到真实后端数据。重点是规则 Markdown、版本切换、审核和上线拦截。</p>
        <div class="card-links">
          <a class="link-chip" href="./day-2.html">打开日视图</a>
          <a class="link-chip" href="../agent%20week%20plan/day_2_rule_center_integration.md">周计划</a>
          <a class="link-chip" href="../agent%20week%20plan/day_2_rule_center_integration.md">合并文档</a>
        </div>
      </section>
      <section class="card tone-warm">
        <h3>Day 3 语义本体 MVP</h3>
        <p>建立 8 字段语义解析协议，让报销、应收、应付、知识查询进入同一结构，给 Orchestrator、User Agent、Hermes 统一消费。</p>
        <div class="card-links">
          <a class="link-chip" href="./day-3.html">打开日视图</a>
          <a class="link-chip" href="../agent%20week%20plan/day_3_semantic_ontology_mvp.md">周计划</a>
          <a class="link-chip" href="../agent%20week%20plan/day_3_semantic_ontology_mvp.md">合并文档</a>
        </div>
      </section>
      <section class="card">
        <h3>Day 4 Orchestrator 运行时</h3>
        <p>把用户消息和定时任务统一接到 Orchestrator，完成 run_id、权限拦截、Agent 路由、ToolCall 和 Trace。</p>
        <div class="card-links">
          <a class="link-chip" href="./day-4.html">打开日视图</a>
          <a class="link-chip" href="../agent%20week%20plan/day_4_orchestrator_runtime.md">周计划</a>
          <a class="link-chip" href="../agent%20week%20plan/day_4_orchestrator_runtime.md">合并文档</a>
        </div>
      </section>
      <section class="card tone-teal">
        <h3>Day 5 User Agent MVP</h3>
        <p>面向用户的问答和流程辅助层。做查询、解释、规则引用、草稿生成，但严格不碰自动审批、自动付款和自动上线。</p>
        <div class="card-links">
          <a class="link-chip" href="./day-5.html">打开日视图</a>
          <a class="link-chip" href="../agent%20week%20plan/day_5_user_agent_mvp.md">周计划</a>
          <a class="link-chip" href="../agent%20week%20plan/day_5_user_agent_mvp.md">合并文档</a>
        </div>
      </section>
      <section class="card tone-olive">
        <h3>Day 6 Hermes MVP</h3>
        <p>后台数字员工层。做任务触发、风险巡检、日报统计、OCR Mock、知识候选、规则草稿，结果都必须可追溯。</p>
        <div class="card-links">
          <a class="link-chip" href="./day-6.html">打开日视图</a>
          <a class="link-chip" href="../agent%20week%20plan/day_6_hermes_mvp.md">周计划</a>
          <a class="link-chip" href="../agent%20week%20plan/day_6_hermes_mvp.md">合并文档</a>
        </div>
      </section>
      <section class="card tone-accent">
        <h3>Day 7 加固、演示和验收</h3>
        <p>不再大扩功能，只做回归、权限边界、审计、Trace、测试、演示脚本和交接收口，让整周产出可跑、可演示、可继续接手。</p>
        <div class="card-links">
          <a class="link-chip" href="./day-7.html">打开日视图</a>
          <a class="link-chip" href="../agent%20week%20plan/day_7_hardening_demo_acceptance.md">周计划</a>
          <a class="link-chip" href="../agent%20week%20plan/day_7_hardening_demo_acceptance.md">合并文档</a>
        </div>
      </section>
    </div>

    <div class="section-kicker">Dependency Chain</div>
    <h2 class="section-title">跨天依赖链</h2>
    <div class="timeline">
      <div class="timeline-step"><strong>Day 1</strong>模型、审计、运行日志、最小业务数据源</div>
      <div class="timeline-step"><strong>Day 2</strong>把 Day 1 的资产 API 接进规则中心 UI</div>
      <div class="timeline-step"><strong>Day 3</strong>在 Day 1/2 基础上产出统一语义结构</div>
      <div class="timeline-step"><strong>Day 4</strong>用 Day 3 的语义结果完成路由与权限</div>
      <div class="timeline-step"><strong>Day 5</strong>接入 User Agent 问答、解释和草稿</div>
      <div class="timeline-step"><strong>Day 6</strong>接入 Hermes 任务、巡检和知识/规则候选</div>
      <div class="timeline-step"><strong>Day 7</strong>统一回归、补日志、做演示和交接</div>
    </div>

    <div class="footer">
      打开顺序建议：<a href="./day-1.html">Day 1</a> 到 <a href="./day-7.html">Day 7</a>。真正执行时，仍以原始 Markdown 为准，这套 HTML 负责加速定位和浏览。
    </div>
  </div>
</body>
</html>