{
  "name": "客户经营大脑 Wiki",
  "version": "1.1.0",
  "updated": "2026-09-22",
  "authority": "CURRENT_STATE",
  "agent_id": "180ac01f-bdd4-4338-a392-24175025f116",
  "grokbot": "grokbot://app/v1/sidebar?agent=180ac01f-bdd4-4338-a392-24175025f116",
  "cards": "agent/cards.json",
  "pages": [
    {
      "path": "index.html",
      "title": "首页",
      "layer": "home",
      "summary": "权威摘要与四入口"
    },
    {
      "path": "state.html",
      "title": "CURRENT_STATE",
      "layer": "authority",
      "summary": "唯一当前权威"
    },
    {
      "path": "tasks.html",
      "title": "派活",
      "layer": "ops",
      "summary": "预设派活指令"
    },
    {
      "path": "nav.html",
      "title": "全站导航",
      "layer": "wiki",
      "summary": "目录树"
    },
    {
      "path": "how.html",
      "title": "怎么学",
      "layer": "learning",
      "summary": "怎么学 + 知识卡片合同"
    },
    {
      "path": "cards/index.html",
      "title": "知识卡片",
      "layer": "cards",
      "summary": "按主题查问题（默认）"
    },
    {
      "path": "agent/cards.json",
      "title": "cards.json",
      "layer": "cards",
      "summary": "主卡结构化导出"
    },
    {
      "path": "claims/index.html",
      "title": "Claims 索引",
      "layer": "claims",
      "summary": "按来源蒸馏原料视图"
    },
    {
      "path": "sources/index.html",
      "title": "原文索引",
      "layer": "source",
      "summary": "原料分组"
    },
    {
      "path": "architecture/agent-embedding.html",
      "title": "Agent 嵌入",
      "layer": "architecture",
      "summary": "- 每位客户有持续状态与记忆；Agent 由事件按需唤醒"
    },
    {
      "path": "architecture/brain-six-layers.html",
      "title": "客户经营大脑 · 六层对照",
      "layer": "architecture",
      "summary": "工作名「客户经营大脑」。本页对照用友 P01 与 PDF A 六层，不另立第三套分层权威。实施口径仍以文三为主参考；分层是沟通语言。"
    },
    {
      "path": "architecture/context-service.html",
      "title": "场景上下文服务",
      "layer": "architecture",
      "summary": "促进成交｜产品匹配｜主动服务｜主动安抚｜主动关怀｜经营与产品洞察"
    },
    {
      "path": "architecture/layers.html",
      "title": "架构分层",
      "layer": "architecture",
      "summary": "多源感知 → 证据与业务事实 → 客户认知内核 → 场景上下文 → Agent 与顾问协同 → 受控执行 → 结果反馈"
    },
    {
      "path": "cards/K-001-not-cdp.html",
      "title": "是不是下一代 CDP？",
      "layer": "cards",
      "summary": "主题主卡 · K-001 · 判断 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-002-naming-context-os.html",
      "title": "工作名/正式名怎么叫？「操作系统」算不算正式名？",
      "layer": "cards",
      "summary": "主题主卡 · K-002 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-003-graphiti-first-phase.html",
      "title": "首期要不要上图数据库？",
      "layer": "cards",
      "summary": "主题主卡 · K-003 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-004-langgraph-first-phase.html",
      "title": "首期要不要上编排全家桶？",
      "layer": "cards",
      "summary": "主题主卡 · K-004 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-005-promise-ledger-leverage.html",
      "title": "承诺账本是否第一杠杆？",
      "layer": "cards",
      "summary": "主题主卡 · K-005 · 判断 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-006-dual-scenario-second-city.html",
      "title": "首期先打哪两条场景？第二城怎么排？",
      "layer": "cards",
      "summary": "主题主卡 · K-006 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-007-golden-context.html",
      "title": "开口前要看清哪五件事？",
      "layer": "cards",
      "summary": "主题主卡 · K-007 · 概念 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-008-phase1-wont-do.html",
      "title": "一期明确不做哪些？",
      "layer": "cards",
      "summary": "主题主卡 · K-008 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-009-voice-platform-relation.html",
      "title": "语音系统和大脑谁干什么？",
      "layer": "cards",
      "summary": "主题主卡 · K-009 · 判断 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-010-trust-tiers-t0-t3.html",
      "title": "证据可信度怎么分档？",
      "layer": "cards",
      "summary": "主题主卡 · K-010 · 概念 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-011-hitl-must-approve.html",
      "title": "哪些动作必须人点头？",
      "layer": "cards",
      "summary": "主题主卡 · K-011 · 实践 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-012-iceberg-context-lake.html",
      "title": "首期要不要默认上数据湖？",
      "layer": "cards",
      "summary": "主题主卡 · K-012 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-013-phase1-scene-service-progress.html",
      "title": "一期要不要改成「只做维修进度推送」？",
      "layer": "cards",
      "summary": "主题主卡 · K-013 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-014-memory-measure-before-select.html",
      "title": "记忆组件要不要先实测再选型？",
      "layer": "cards",
      "summary": "主题主卡 · K-014 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-015-dialogue-not-master-data.html",
      "title": "聊天能不能改正式到账和交期？",
      "layer": "cards",
      "summary": "主题主卡 · K-015 · 判断 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-016-three-progress-lines.html",
      "title": "交付、沟通、承诺能不能混成一条进度？",
      "layer": "cards",
      "summary": "主题主卡 · K-016 · 决策 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-017-three-understanding-objects.html",
      "title": "持续理解要看清哪三类？",
      "layer": "cards",
      "summary": "主题主卡 · K-017 · 概念 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-018-task-context-capability-catalog.html",
      "title": "任务上下文是什么？等于执行接口吗？",
      "layer": "cards",
      "summary": "主题主卡 · K-018 · 概念 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "cards/K-019-sales-pilot-with-pr7.html",
      "title": "销售试点怎么用脱敏语料起步？先离线还是先接 CRM？",
      "layer": "cards",
      "summary": "主题主卡 · K-019 · 实践 · 权威见 ../CURRENTSTATE.md"
    },
    {
      "path": "claims/2026-09-20-architecture-practice.html",
      "title": "Claims · 2026-09-20 架构实践文蒸馏（第二篇）",
      "layer": "claims",
      "summary": "原料：../sources/raw/2026-09-20-architecture-practice.md"
    },
    {
      "path": "claims/2026-09-20-customer-os-memory-agent.html",
      "title": "Claims · 2026-09-20 客户记忆+Agent+闭环（第四篇）蒸馏",
      "layer": "claims",
      "summary": "文四为探索设计/待业务选择。技术断言一律 待核实；强化文一/文三，不推翻既有收敛。"
    },
    {
      "path": "claims/2026-09-20-engine-blueprint-dual-pilot.html",
      "title": "Claims · 2026-09-20 引擎蓝图与双场景试点（PDF B）蒸馏",
      "layer": "claims",
      "summary": "PDF B 边界：未运行客户数据评测；未验证长城生产接口。开源裁决为选型建议，非已安装。"
    },
    {
      "path": "claims/2026-09-20-second-city-context-os.html",
      "title": "Claims · 2026-09-20 第二城 Context OS（PDF A）蒸馏",
      "layer": "claims",
      "summary": "PDF A 为探索方案。产品叙事强采纳；技术「默认栈」降为条件选；「第一闭环=交车延误」记为第二城优先打穿切片，不 silently 推翻购车推进主场景。"
    },
    {
      "path": "claims/2026-09-20-voice-to-customer-engine.html",
      "title": "Claims · 2026-09-20 Voice→客户理解与行动引擎（第三篇）蒸馏",
      "layer": "claims",
      "summary": "文三自称探索设计/待业务选择。凡技术断言一律 待核实，勿写成已上线或已批准规格。"
    },
    {
      "path": "claims/2026-09-20-workshop.html",
      "title": "Claims · 2026-09-20 Workshop 研究报告蒸馏",
      "layer": "claims",
      "summary": "原料：../sources/raw/2026-09-20-workshop-research.md"
    },
    {
      "path": "claims/2026-09-20-yonyou-pptx.html",
      "title": "Claims · 2026-09-20 用友 PPT（客户经营大脑）蒸馏",
      "layer": "claims",
      "summary": "目标架构 / 设计方案，非现状声明。工作名「客户经营大脑」由此视觉对齐。"
    },
    {
      "path": "claims/2026-09-21-full-site-audio-review.html",
      "title": "Claims · 2026-09-21 全站与音频综合审阅蒸馏",
      "layer": "claims",
      "summary": "建议稿→本库开始执行回写。 讨论稿 ≠ 已批准规格 ≠ 生产验证。行业公开链接只支持方向说明。同源站点摘要/音频转写出现三次仍可能一条来源。"
    },
    {
      "path": "claims/2026-09-21-kimi-customer-engine.html",
      "title": "Claims · 2026-09-21 KIMI（AI 原生客户引擎）蒸馏",
      "layer": "claims",
      "summary": "探索/建议设计 ≠ 已批准规格。厂商自报效果数字一律上限/待核实。"
    },
    {
      "path": "claims/2026-09-21-wiki-knowledge-audit.html",
      "title": "Claims · 2026-09-21 Wiki 知识管理评审蒸馏",
      "layer": "claims",
      "summary": "本页为按来源蒸馏的原料视图。默认问答请走知识卡片。"
    },
    {
      "path": "entities/industry-refs.html",
      "title": "行业与开源参照",
      "layer": "entities",
      "summary": "每行提醒：厂商介绍 ≠ 独立效果验证；开源未在友车环境实测。"
    },
    {
      "path": "nav-index.html",
      "title": "客户经营大脑 · Agent 运营 Wiki",
      "layer": "wiki",
      "summary": "工作名：客户经营大脑 · 工程名：客户理解与行动引擎 · Customer Context OS = 别名/噪音"
    },
    {
      "path": "learning/log.html",
      "title": "学习日志",
      "layer": "learning",
      "summary": "- 事件： 按亮哥已点头口径，优化 Wiki 日常入口人话：首页 hero/现在/四件事/原文后移；CURRENTSTATE 顶部加人话导读；19 张主卡 shortanswer 白话化；A/B 场景与销售试点文首加人话说明；对齐 plai…"
    },
    {
      "path": "ops/acceptance.html",
      "title": "验收",
      "layer": "ops",
      "summary": "建议生成 → 顾问采纳 → 实际执行 → 业务完成 → 问题解决"
    },
    {
      "path": "ops/handoff-prompt-mp3-customer-brain.html",
      "title": "交接提示词 · MP3 × 客户经营大脑（给全新 Agent / 新对话）",
      "layer": "ops",
      "summary": "复制下方「提示词正文」整段交给新项目即可。本文件仅存档。日期 2026-09-21。"
    },
    {
      "path": "ops/mvp-four.html",
      "title": "MVP 四件套 ↔ 下一步四交付物",
      "layer": "ops",
      "summary": "不另起平行清单。 开工只维护「下一步四交付物」；MVP 四件是体验/验收切口视角。"
    },
    {
      "path": "ops/next-deliverables.html",
      "title": "下一步四交付物",
      "layer": "ops",
      "summary": "场景草案骨架已见：../scenarios/A-sales-next-action.md · ../scenarios/B-promise-comfort.md"
    },
    {
      "path": "ops/pilot-12w.html",
      "title": "12 周试点节奏",
      "layer": "ops",
      "summary": "状态：计划草案 · 试点未开始 · 待确认"
    },
    {
      "path": "ops/sales-pilot-pr7-corpus.html",
      "title": "销售侧客户引擎试点方案（PR7 语料对齐）",
      "layer": "ops",
      "summary": "语料：MP3 PR 7（已合并）researchcorpus/2026-09-21 · 对照：../syntheses/pr7-corpus-vs-engine-2026-09-21.md"
    },
    {
      "path": "ops/second-city-14-90.html",
      "title": "第二城 · 14 天裁定 → 90 天节奏",
      "layer": "ops",
      "summary": "城市/门店待业务指定。 以下为探索节奏，非已批准项目计划。"
    },
    {
      "path": "ops/six-questions.html",
      "title": "六件事 · 待业务回答（文三第十八节）",
      "layer": "ops",
      "summary": "未得书面回答前，Wiki 只维护影子与实验记录，不宣称规格生效。"
    },
    {
      "path": "product/definition.html",
      "title": "产品定义",
      "layer": "product",
      "summary": "AI 原生客户认知与行动引擎 = 连接交互证据、业务事实、人车关系、履约能力的共享内核。认知与行动缺一不可。"
    },
    {
      "path": "product/info-kinds.html",
      "title": "四种信息性质",
      "layer": "product",
      "summary": "- 上下文包必须标清：事实 vs 推断 vs 缺口"
    },
    {
      "path": "product/memory-kinds.html",
      "title": "四类记忆",
      "layer": "product",
      "summary": "群体边界（勿混）：群体规律 ≠ 个人事实；相关 ≠ 因果；公开投诉 ≠ 故障率。"
    },
    {
      "path": "product/object-model.html",
      "title": "对象模型（八类）",
      "layer": "product",
      "summary": "- 承诺管理比兴趣标签更有价值（推断，待验证）"
    },
    {
      "path": "scenarios/A-sales-next-action.html",
      "title": "场景 A · 销售理解与下一步行动（草案 · 待确认）",
      "layer": "scenarios",
      "summary": "场景是什么： 客户试驾后（或看车过程中）说「再考虑考虑 / 回去商量」时，帮顾问在开口前整理清楚：已知需求、可能卡点、还没核实的点、建议体验动作、需要当面澄清的问题。"
    },
    {
      "path": "scenarios/B-promise-comfort.html",
      "title": "场景 B · 交付/缺件承诺追踪与主动安抚（草案 · 待确认）",
      "layer": "scenarios",
      "summary": "场景是什么： 交车延误、维修待件、答应过的节点快到期或已逾期时，把「客户原话 + 我们答应过什么 + 业务系统里的实际进度」对上号，再给出可办方案与行动卡，并追踪有没有兑现。"
    },
    {
      "path": "sources/2026-09-20-architecture-practice-index.html",
      "title": "来源索引 · 2026-09-20 架构设计与落地实践文（第二篇）",
      "layer": "source",
      "summary": "第二篇主张：传统 CDP/宽表标签在汽车长周期、多模态下结构性不够；应以 Context Lake + 双时态时序知识图谱 + LangGraph 多智能体，形成「前向赋能 / 后向反哺」闭环，并延伸到 GLoM 群体泛化。文中含三代演进、…"
    },
    {
      "path": "sources/2026-09-20-customer-os-memory-agent-index.html",
      "title": "来源索引 · 2026-09-20 客户记忆 + Agent + 闭环行动（第四篇）",
      "layer": "source",
      "summary": "第四篇主张：不是下一代 CDP，而是 Customer Intelligence & Action Engine（本库名「客户引擎」）；文中「Customer OS」标噪音防膨胀。闭环 Observe→Understand→Remember…"
    },
    {
      "path": "sources/2026-09-20-engine-blueprint-dual-pilot-index.html",
      "title": "来源索引 · 2026-09-20 行业调研与双场景试点蓝图（PDF B）",
      "layer": "source",
      "summary": "建议设计稿：定位「客户理解与行动引擎」；六问作产品主线；CDP 底座能力仍有价值，升级的是使用方式；理解+行动并重；八对象；活客户理解卡；ASR 六步语义关联；数据分区（原始证据/客户事项/检索索引/分析/知识）；双场景销售+车主服务；开源…"
    },
    {
      "path": "sources/2026-09-20-research-index.html",
      "title": "来源索引 · 2026-09-20 研究报告",
      "layer": "source",
      "summary": "一份关于「AI 原生客户认知与行动引擎」的 workshop 研究报告：建议从记录型 CDP 转向持续理解 + 受控行动 + 结果学习；保留Voice Platform；首期 A/B 两场景；开源与模型仅作候选。"
    },
    {
      "path": "sources/2026-09-20-second-city-context-os-index.html",
      "title": "来源索引 · 2026-09-20 第二城 Customer Context OS（PDF A）",
      "layer": "source",
      "summary": "第二城探索方案：产品叙事「客户引擎 / Customer Context OS」——不是又一个 CDP；对象是 Golden Context（人是谁 + 此刻要达成什么 + 已试过什么 + 客户怎么反应 + 答应过什么）。四耗散（身份/语料…"
    },
    {
      "path": "sources/2026-09-20-voice-to-customer-engine-index.html",
      "title": "来源索引 · 2026-09-20 Voice→客户理解与行动引擎（第三篇）",
      "layer": "source",
      "summary": "第三篇自称探索设计 / 待业务选择：从 Voice Platform 收敛到「客户理解与行动引擎」。核心：五问；三类可核实状态（表达/承诺/业务实际）；三产品（顾问伙伴/上下文服务/经营学习）；成功标准看需求解决·承诺履行·顾问省时；首期购…"
    },
    {
      "path": "sources/2026-09-20-yonyou-pptx-index.html",
      "title": "来源索引 · 2026-09-20 用友 PPT（客户经营大脑设计）",
      "layer": "source",
      "summary": "用友 12 页设计幻灯（目标架构非现状）：六层总体架构；人车事项与证据关联；接入八步；数据分层（正式核心在关系库，索引可重建）；可信理解（身份+证据+时间）；场景上下文按任务取数；Agent A0–A3 授权；交车延期闭环示例；双向学习三闸…"
    },
    {
      "path": "sources/2026-09-21-full-site-audio-review-index.html",
      "title": "来源索引 · 2026-09-21 全站与音频综合审阅",
      "layer": "source",
      "summary": "亮哥讨论稿：对公开 Wiki 站 + 原件 + 三段音频的综合审阅。建议稿（未接生产、未改线上）。保留产品定位与承诺账本，校正八处表述；明确三理解对象、五组核心、任务上下文、四类智能体逻辑能力；默认双场景微调；技术基线与 Graphiti …"
    },
    {
      "path": "sources/2026-09-21-kimi-customer-engine-index.html",
      "title": "来源索引 · 2026-09-21 KIMI（AI 原生客户引擎调研与架构）",
      "layer": "source",
      "summary": "KIMI 长文报告 + 立项汇报 PPT（20 页）。核心建议：不升级 CDP，建 AI 原生客户引擎；一期场景建议「维修进度主动推送」；记忆组件不预选型、先 golden set；身份主权自持；七层 L0–L6；12 月四阶段；预算区间为…"
    },
    {
      "path": "sources/raw/2026-09-20-architecture-practice.html",
      "title": "汽车全生命周期AI原生客户认知引擎系统架构设计与落地实践",
      "layer": "source",
      "summary": "- 注意：文中技术选型与评分数值为作者论述，非友车实测"
    },
    {
      "path": "sources/raw/2026-09-20-customer-os-memory-agent.html",
      "title": "AI 原生客户智能与行动引擎：从 CRM/CDP 走向「客户记忆 + Agent + 闭环行动」的汽车客户平台",
      "layer": "source",
      "summary": "⚠️ 重建稿 ≠ 一手原文。 Task prompt 截断后按要点结构化重建；措辞与章节编号待作者机/原文复核。架构图与原件以 originals / 整页图为准。"
    },
    {
      "path": "sources/raw/2026-09-20-engine-blueprint-dual-pilot.html",
      "title": "客户理解与行动引擎｜行业调研、产品蓝图与双场景试点",
      "layer": "source",
      "summary": "- 性质：建议设计稿（行业调研 + 产品蓝图 + 双场景试点；不是已批准规格）"
    },
    {
      "path": "sources/raw/2026-09-20-pptx-extract.html",
      "title": "PPT 抽取 · 客户经营大脑相关",
      "layer": "source",
      "summary": "- 源文件: 5726183fe52ff3fd7c90df22308d445c1ba179ed5b0fb8110179a12bfc57f421.pptx"
    },
    {
      "path": "sources/raw/2026-09-20-second-city-context-os.html",
      "title": "客户引擎 / Customer Context OS · SECOND CITY",
      "layer": "source",
      "summary": "- 性质：探索方案（第二城产品与架构草案；不是已批准规格，也不是已实施能力）"
    },
    {
      "path": "sources/raw/2026-09-20-voice-to-customer-engine.html",
      "title": "从 Voice Platform 到 AI 原生客户理解与行动引擎",
      "layer": "source",
      "summary": "⚠️ 重建稿 ≠ 一手原文。 Task prompt 截断后按要点结构化重建；措辞与章节编号待作者机/原文复核。架构图与原件以 originals / 整页图为准。"
    },
    {
      "path": "sources/raw/2026-09-20-workshop-research.html",
      "title": "AI 原生客户认知与行动引擎",
      "layer": "source",
      "summary": "保留现有Voice Platform作为重要感知入口；建立一个有证据、会更新的客户内核；按不同场景向顾问和 Agent 提供业务上下文；通过正式业务系统完成行动；再用真实结果反过来改进对客户和业务的理解。"
    },
    {
      "path": "sources/raw/2026-09-20-yonyou-pptx-design.html",
      "title": "用友 PPT 设计摘要 · 客户经营大脑（P01–P12）",
      "layer": "source",
      "summary": "- 性质：设计方案幻灯（目标架构 / 设计方案，非现状声明）"
    },
    {
      "path": "sources/raw/2026-09-21-full-site-audio-review.html",
      "title": "全站与音频综合审阅 · 结构化摘要",
      "layer": "source",
      "summary": "- 性质：讨论稿 / 建议（未接生产、未改线上、未验证经营效果）"
    },
    {
      "path": "sources/raw/2026-09-21-kimi-customer-engine-report.html",
      "title": "KIMI · AI 原生客户引擎：深度调研与架构设计报告（结构化摘要）",
      "layer": "source",
      "summary": "全文原件（约 269KB）见 originals/2026-09-21-kimi-customer-engine-report.md"
    },
    {
      "path": "sources/raw/2026-09-21-wiki-knowledge-audit.html",
      "title": "Wiki 知识管理评审要点（入库原料）",
      "layer": "source",
      "summary": "状态： 建议稿；2026-09-21；未改站时写成；现已开始执行第一批（主卡 + 规则 + 导出）。"
    },
    {
      "path": "sources/raw/originals/2026-09-21-full-site-audio-review.html",
      "title": "客户经营大脑：全站与音频综合审阅",
      "layer": "source",
      "summary": "材料性质：讨论稿 / 建议 / 未接生产 / 未改线上。 本库吸收口径：建议稿→本库开始执行回写（明确校正入 CURRENTSTATE 与主卡；非生产已验证）。"
    },
    {
      "path": "sources/raw/originals/2026-09-21-kimi-customer-engine-report.html",
      "title": "AI 原生客户引擎：深度调研与架构设计报告——汽车客户全生命周期的数据、智能与 Agent 体系",
      "layer": "source",
      "summary": "表注：落地批次 P 批次↔期次映射以第 10 章路线图为唯一口径——P0 对应一期；P1/P2 与期次的对应关系参照第 10 章，本章不再单列期次归属。"
    },
    {
      "path": "syntheses/four-papers-2026-09-20.html",
      "title": "四文对照综合 · 2026-09-20",
      "layer": "synthesis",
      "summary": "独立判断：不迎合任一作者。探索设计≠规格；推断≠事实；开源未实测；「Customer OS」防膨胀。"
    },
    {
      "path": "syntheses/full-review-vs-current-2026-09-21.html",
      "title": "综合审阅 vs CURRENTSTATE / K-001…K-014 / KIMI · 2026-09-21",
      "layer": "synthesis",
      "summary": "讨论稿建议。本表记录共识 / 分歧 / 本库独立裁决（执行回写项）。"
    },
    {
      "path": "syntheses/kimi-vs-current-2026-09-21.html",
      "title": "综合 · KIMI vs 本库权威（2026-09-21）",
      "layer": "synthesis",
      "summary": "独立判断：不迎合报告。原料 ≠ 结论。厂商数字 = 上限。"
    },
    {
      "path": "syntheses/materials-2026-09-20-pack.html",
      "title": "材料包对照 · 2026-09-20（四文 + 用友 PPT + 两 PDF）",
      "layer": "synthesis",
      "summary": "独立判断：不迎合任一作者。探索/建议设计 ≠ 规格。CURRENTSTATE 唯一权威。"
    },
    {
      "path": "syntheses/plain-language-all-sources-2026-09-22.html",
      "title": "客户经营大脑 · 全原料人话蒸馏（给亮哥）",
      "layer": "synthesis",
      "summary": "蒸馏日： 2026-09-22（Asia/Shanghai）"
    },
    {
      "path": "syntheses/pr7-corpus-vs-engine-2026-09-21.html",
      "title": "PR7 语料能力 vs 客户经营大脑对象缺口 · 2026-09-21",
      "layer": "synthesis",
      "summary": "假名研究包可分析；不是金标、不是生产备份、不是不可逆匿名。合作方/隔离默认不提取。"
    },
    {
      "path": "syntheses/three-papers-2026-09-20.html",
      "title": "三文对照综合 · 2026-09-20",
      "layer": "synthesis",
      "summary": "独立判断：不迎合任一作者。探索设计≠规格；推断≠事实；开源未实测；mp3 仓未挂载。"
    },
    {
      "path": "syntheses/two-papers-2026-09-20.html",
      "title": "两文对照综合 · 2026-09-20",
      "layer": "synthesis",
      "summary": "独立判断：不迎合任一作者。推断≠事实；厂商/架构蓝图≠效果验证；开源未在友车实测。"
    },
    {
      "path": "tech/first-stack.html",
      "title": "首期技术路线",
      "layer": "tech",
      "summary": "现有声音 + 结构化客户内核 + 混合检索 + 场景上下文服务 + 少量受控 Agent + 评估追踪"
    },
    {
      "path": "tech/models.html",
      "title": "模型按任务",
      "layer": "tech",
      "summary": "公开资料核验截至 2026-09-20；未在友车环境完成选型实测。"
    },
    {
      "path": "tech/opensource.html",
      "title": "开源候选",
      "layer": "tech",
      "summary": "开源未在友车数据与环境实测。 厂商/项目介绍 ≠ 效果验证。"
    },
    {
      "path": "syntheses/index.html",
      "title": "综合索引",
      "layer": "synthesis",
      "summary": "综合索引"
    },
    {
      "path": "architecture/index.html",
      "title": "架构索引",
      "layer": "architecture",
      "summary": "架构索引"
    },
    {
      "path": "product/index.html",
      "title": "产品索引",
      "layer": "product",
      "summary": "产品索引"
    },
    {
      "path": "ops/index.html",
      "title": "运营索引",
      "layer": "ops",
      "summary": "运营索引"
    },
    {
      "path": "tech/index.html",
      "title": "技术索引",
      "layer": "tech",
      "summary": "技术索引"
    },
    {
      "path": "scenarios/index.html",
      "title": "场景索引",
      "layer": "scenarios",
      "summary": "场景索引"
    },
    {
      "path": "learning/index.html",
      "title": "学习索引",
      "layer": "learning",
      "summary": "学习索引"
    },
    {
      "path": "entities/index.html",
      "title": "实体索引",
      "layer": "entities",
      "summary": "实体索引"
    }
  ],
  "tasks": [
    {
      "id": "update-state",
      "title": "a. 更新 CURRENT_STATE 某方向",
      "desc": "把某条已拍板/待确认方向写入或修订权威文件，并重建站点。",
      "prompt": "【派活 · 客户经营大脑 Wiki】\n请更新 CURRENT_STATE.md 中「已拍板方向」的某一条（或新增一条）。\n要求：\n1. 先读 /workspace/wiki/customer-engine/CURRENT_STATE.md，确认当前表述；\n2. 说明要改的方向、新状态（共识/待确认/入库约束等）、依据材料路径；\n3. 只改权威必要段落，不另立第二状态源；\n4. 改完后运行 python3 /workspace/wiki/customer-engine/build_site.py 重建站点；\n5. 回报：改了什么、权威摘要一句、站点页数。\n【请在下方写明具体方向】\n"
    },
    {
      "id": "object-source-table",
      "title": "b. 起草对象与权威来源表",
      "desc": "交付物①：客户对象与权威来源表（含承诺、身份合并、Golden Context 字段）。",
      "prompt": "【派活 · 客户经营大脑 Wiki】\n请起草「客户对象与权威来源表」（下一步四交付物之①）。\n依据：CURRENT_STATE、product/object-model.md、PDF B 八对象、PDF A Golden Context。\n要求：\n1. 列出对象、权威来源系统、字段/证据、更新节奏、负责人角色；\n2. 含承诺对象、身份合并规则、Golden Context 字段；\n3. 写入合适路径（建议 product/ 或 ops/ 新页），并在 CURRENT_STATE 入口导航挂链；\n4. 重建站点并回报路径。\n"
    },
    {
      "id": "scenario-contract",
      "title": "c. 起草 A/B 或交车延误场景合同",
      "desc": "交付物②：购车推进 / 延期关怀 / 第二城交车延误切片合同。",
      "prompt": "【派活 · 客户经营大脑 Wiki】\n请起草场景合同（任选：A 购车推进 / B 延期关怀 / 第二城交车延误优先打穿切片）。\n依据：scenarios/A、scenarios/B、ops/second-city-14-90、CURRENT_STATE 首期场景。\n合同需含：触发、输入上下文、允许行动、HITL 门槛、成功指标、明确不做、验收反例。\n写回 scenarios/ 或 ops/，更新 CURRENT_STATE 若有裁决变化，重建站点。\n"
    },
    {
      "id": "ingest-materials",
      "title": "d. 吸收新材料进 Wiki 并重建站点",
      "desc": "把新 PDF/PPT/研究报告蒸馏进 claims / sources / syntheses，更新权威。",
      "prompt": "【派活 · 客户经营大脑 Wiki】\n请吸收新材料进客户经营大脑 Wiki。\n流程：\n1. 原料放入 sources/raw/（可先 txt/md 抽取）；\n2. 写 sources/*-index.md 与 claims/* 蒸馏（条条可复核）；\n3. 必要时更新 syntheses/ 对照与 CURRENT_STATE 权威摘要；\n4. 明确：原料≠结论；权威只在 CURRENT_STATE；\n5. python3 build_site.py 重建；回报新增页与权威变更。\n【请附上材料路径或粘贴要点】\n"
    },
    {
      "id": "second-city-checklist",
      "title": "e. 第二城 14 天试点检查清单",
      "desc": "基于 ops/second-city-14-90 产出可执行 14 天裁定检查清单。",
      "prompt": "【派活 · 客户经营大脑 Wiki】\n请基于 ops/second-city-14-90.md 与 CURRENT_STATE，起草「第二城 14 天试点检查清单」。\n要求：按日或按关卡列出裁定项、通过/不通过标准、停扩线触发条件；\n优先打穿：交车延误安抚；购车推进可并行不撤。\n写到 ops/ 新页并挂到权威入口，重建站点。\n"
    }
  ]
}