{ "meta": { "title": "FDE Insight 领域知识图谱", "version": "2.1.0", "schemaVersion": "1.0.0", "language": "zh-CN", "updated": "2026-08-09", "sourcePolicy": "报告结论、工程判断和需要重新核验的信息必须保持可区分。", "generatedFrom": "knowledge/report-analysis.json" }, "nodes": [ { "id": "principle-frontline-learning", "type": "principle", "name": "前线学习", "nameEn": "Frontline learning", "definition": "交付和学习同时发生，客户现场暴露的问题必须回流为下一次部署可复用的能力。", "sourceRefs": ["report:p14-17"] }, { "id": "principle-80-95-99", "type": "principle", "name": "80/95/99 规律", "nameEn": "80/95/99 rule", "definition": "原型覆盖常见路径并不等于生产可用，后续精度来自真实数据、评测、治理和人工兜底。", "sourceRefs": ["report:p9-10"] }, { "id": "principle-sedimentation-first", "type": "principle", "name": "沉淀优先", "nameEn": "Sedimentation first", "definition": "项目结束前明确哪些经验进入 Skill、连接器、评测集、模板、本体或产品基线。", "sourceRefs": ["report:p4", "report:p16-17"] }, { "id": "principle-human-fallback", "type": "principle", "name": "人工兜底", "nameEn": "Human fallback", "definition": "高风险和低置信任务必须允许人工审核、接管、回滚和责任追溯，不能追求盲目的全自动。", "sourceRefs": ["report:p10", "report:p28-30"] }, { "id": "principle-value-before-model", "type": "principle", "name": "业务价值先于模型能力", "nameEn": "Value before model", "definition": "先定义业务决策、流程变化和衡量口径，再选择模型、工具与工程方案。", "sourceRefs": ["report:p8-10", "project:synthesis"] }, { "id": "principle-three-party-loop", "type": "principle", "name": "平台伙伴客户协同", "nameEn": "Platform partner customer loop", "definition": "原厂验证平台和标杆，伙伴复制与本地化，客户逐步形成自助构建和持续运营能力。", "sourceRefs": ["report:p36", "report:p59-60"] }, { "id": "role-fde", "type": "role", "name": "前线部署工程师", "nameEn": "Forward Deployed Engineer", "definition": "深入客户现场，把模糊业务问题转为可运行结果，并把经验带回产品和知识资产。", "sourceRefs": ["report:p8", "report:p14-17"] }, { "id": "role-echo", "type": "role", "name": "Echo 角色", "nameEn": "Echo role", "definition": "负责抽象行业共性、组织知识蒸馏、维护本体基线，并判断哪些反馈值得进入公共资产。", "sourceRefs": ["report:p14-17", "report:p47-56"] }, { "id": "role-delta", "type": "role", "name": "Delta 角色", "nameEn": "Delta role", "definition": "负责客户前线的原型、集成、调优和上线，把现场差异转成可验证的工程反馈。", "sourceRefs": ["report:p14-17", "report:p47-56"] }, { "id": "role-customer-sponsor", "type": "role", "name": "客户业务负责人", "nameEn": "Customer sponsor", "definition": "为项目提供业务授权、资源和考核牵引，对采用率和业务结果负责，而不只是审批预算。", "sourceRefs": ["report:p28-30", "report:p38-40"] }, { "id": "role-platform-team", "type": "role", "name": "平台产品团队", "nameEn": "Platform product team", "definition": "吸收高频前线反馈，把单点解决方案升级为标准能力、接口、治理机制和开发工具。", "sourceRefs": ["report:p14-17", "report:p32-36"] }, { "id": "role-ecosystem-partner", "type": "role", "name": "生态交付伙伴", "nameEn": "Ecosystem delivery partner", "definition": "基于标准工具和行业模板扩大覆盖，并承担本地化适配、培训和持续运营服务。", "sourceRefs": ["report:p36", "report:p59-60"] }, { "id": "stage-discovery", "type": "stage", "name": "场景发现", "nameEn": "Discovery", "definition": "通过访谈和流程观察识别高价值问题、用户、约束、责任边界和可量化基线。", "sourceRefs": ["report:p28-30", "report:p47-48"] }, { "id": "stage-runnable-demo", "type": "stage", "name": "可运行验证", "nameEn": "Runnable demo", "definition": "用真实或接近真实的数据跑通关键路径，提前暴露模型、数据、接口和采用风险。", "sourceRefs": ["report:p9", "report:p28-30"] }, { "id": "stage-pilot", "type": "stage", "name": "受控试点", "nameEn": "Controlled pilot", "definition": "限定用户、数据和责任范围，在可回滚条件下验证效果、稳定性和流程适配。", "sourceRefs": ["report:p28-30", "project:synthesis"] }, { "id": "stage-production", "type": "stage", "name": "生产上线", "nameEn": "Production", "definition": "完成权限、审计、监控、故障处理、人工接管和运行手册后进入真实业务。", "sourceRefs": ["report:p10", "report:p28-30"] }, { "id": "stage-adoption", "type": "stage", "name": "组织采用", "nameEn": "Adoption", "definition": "把新能力嵌入岗位、流程和考核，通过培训、陪跑和运营形成稳定使用习惯。", "sourceRefs": ["report:p10", "report:p33-35", "report:p38-39"] }, { "id": "stage-reuse", "type": "stage", "name": "沉淀复用", "nameEn": "Reuse", "definition": "复盘客户差异和共性，将验证过的知识资产用于同类客户并降低交付成本。", "sourceRefs": ["report:p16-17", "report:p47-56"] }, { "id": "capability-business-discovery", "type": "capability", "name": "业务发现", "nameEn": "Business discovery", "definition": "从模糊诉求中定位真实用户、关键任务、失败成本、流程约束和价值基线。", "sourceRefs": ["report:p28-30", "report:p69"] }, { "id": "capability-full-stack-delivery", "type": "capability", "name": "全栈交付", "nameEn": "Full-stack delivery", "definition": "能够完成前后端、模型调用、数据处理、部署和现场调试，而不依赖层层转交。", "sourceRefs": ["report:p35", "report:p65-66", "report:p75"] }, { "id": "capability-system-integration", "type": "capability", "name": "系统集成", "nameEn": "System integration", "definition": "连接身份、权限、数据、业务系统和协作入口，并处理接口稳定性与版本变化。", "sourceRefs": ["report:p8-10", "report:p28-30"] }, { "id": "capability-agent-engineering", "type": "capability", "name": "Agent 工程", "nameEn": "Agent engineering", "definition": "设计上下文、工具、状态、权限和多步骤编排，使 Agent 能完成受控业务任务。", "sourceRefs": ["report:p25-26", "report:p79", "project:synthesis"] }, { "id": "capability-evaluation", "type": "capability", "name": "评测与调优", "nameEn": "Evaluation and tuning", "definition": "用真实样本、边界案例和业务口径持续评测，避免只凭演示体验判断效果。", "sourceRefs": ["report:p9-10", "report:p28-30"] }, { "id": "capability-production-governance", "type": "capability", "name": "生产治理", "nameEn": "Production governance", "definition": "建立权限、审计、可观测、回滚、故障响应和人工接管等生产控制。", "sourceRefs": ["report:p10", "report:p28-30"] }, { "id": "capability-change-management", "type": "capability", "name": "组织变革推动", "nameEn": "Change management", "definition": "推动管理层、业务和 IT 对齐目标，把使用责任写入流程、岗位和考核。", "sourceRefs": ["report:p10", "report:p33-35", "report:p42-45"] }, { "id": "capability-knowledge-modeling", "type": "capability", "name": "业务知识建模", "nameEn": "Business knowledge modeling", "definition": "抽象实体、属性、关系、动作、状态和规则，让系统使用稳定的业务语义。", "sourceRefs": ["report:p20-21", "report:p47-56"] }, { "id": "capability-stakeholder-communication", "type": "capability", "name": "关键人沟通", "nameEn": "Stakeholder communication", "definition": "用业务语言解释能力边界、风险和收益，并推动高层与一线形成共同决策。", "sourceRefs": ["report:p33-35", "report:p42-45"] }, { "id": "capability-asset-productization", "type": "capability", "name": "资产产品化", "nameEn": "Asset productization", "definition": "判断现场经验是否具有跨客户价值，并将其整理、评审、版本化和维护。", "sourceRefs": ["report:p14-17", "report:p47-56"] }, { "id": "deliverable-scenario-map", "type": "deliverable", "name": "场景地图", "nameEn": "Scenario map", "definition": "记录目标用户、任务链路、系统边界、风险、价值假设和优先级的发现成果。", "sourceRefs": ["report:p28-30", "project:synthesis"] }, { "id": "deliverable-runnable-demo", "type": "deliverable", "name": "可运行 Demo", "nameEn": "Runnable demo", "definition": "用真实问题跑通关键路径并可现场操作的验证系统，不是仅供展示的静态原型。", "sourceRefs": ["report:p9", "report:p28-30"] }, { "id": "deliverable-production-solution", "type": "deliverable", "name": "生产解决方案", "nameEn": "Production solution", "definition": "已完成系统集成、治理、监控和责任划分，能够承接真实业务流量的方案。", "sourceRefs": ["report:p28-30", "report:p35-36"] }, { "id": "deliverable-evaluation-set", "type": "deliverable", "name": "业务评测集", "nameEn": "Business evaluation set", "definition": "覆盖常见路径、长尾问题、风险边界和历史坏例的可重复评测样本集合。", "sourceRefs": ["report:p4", "report:p9-10", "project:synthesis"] }, { "id": "deliverable-runbook", "type": "deliverable", "name": "生产运行手册", "nameEn": "Production runbook", "definition": "说明监控、报警、故障分级、人工接管、回滚和责任人的日常运行文档。", "sourceRefs": ["report:p28-30", "project:synthesis"] }, { "id": "deliverable-adoption-plan", "type": "deliverable", "name": "采用计划", "nameEn": "Adoption plan", "definition": "明确试点用户、培训、陪跑、岗位变化、运营节奏和使用率目标的执行计划。", "sourceRefs": ["report:p33-35", "report:p38-39"] }, { "id": "deliverable-value-review", "type": "deliverable", "name": "价值复盘", "nameEn": "Value review", "definition": "对照基线汇总业务影响、技术表现、采用情况、风险事件和下一阶段决策。", "sourceRefs": ["report:p29-30", "report:p39", "project:synthesis"] }, { "id": "deliverable-reusable-asset", "type": "deliverable", "name": "可复用资产包", "nameEn": "Reusable asset package", "definition": "项目收尾时提交的 Skill、连接器、模板、评测集、本体更新或产品需求组合。", "sourceRefs": ["report:p16-17", "report:p47-56"] }, { "id": "metric-adoption-rate", "type": "metric", "name": "采用率", "nameEn": "Adoption rate", "definition": "目标用户在约定周期内实际使用新流程或 Agent 的比例，需要结合活跃频次解释。", "sourceRefs": ["report:p29-30", "report:p39", "report:p44"] }, { "id": "metric-task-success-rate", "type": "metric", "name": "任务成功率", "nameEn": "Task success rate", "definition": "在业务验收口径下完整完成任务且不触发严重错误的样本比例。", "sourceRefs": ["report:p9-10", "report:p58-59", "project:synthesis"] }, { "id": "metric-cycle-time", "type": "metric", "name": "流程周期", "nameEn": "Cycle time", "definition": "从任务进入到完成的端到端时间，用于判断 AI 是否真正减少等待和转交。", "sourceRefs": ["report:p29", "report:p58-59", "project:synthesis"] }, { "id": "metric-human-review-rate", "type": "metric", "name": "人工复核率", "nameEn": "Human review rate", "definition": "需要人工判断、纠错或接管的任务比例，用于观察风险与自动化边界。", "sourceRefs": ["report:p10", "report:p28-30", "project:synthesis"] }, { "id": "metric-production-reliability", "type": "metric", "name": "生产可靠性", "nameEn": "Production reliability", "definition": "结合可用性、故障率、恢复时间和异常处置完成度评估系统运行质量。", "sourceRefs": ["report:p28-30", "report:p44", "project:synthesis"] }, { "id": "metric-expansion-rate", "type": "metric", "name": "场景扩展率", "nameEn": "Expansion rate", "definition": "首个场景稳定后进入同一业务链路或相邻部门的新场景比例。", "sourceRefs": ["report:p39", "report:p44", "report:p58-59"] }, { "id": "metric-reuse-rate", "type": "metric", "name": "资产复用率", "nameEn": "Asset reuse rate", "definition": "新项目直接采用既有 Skill、连接器、模板或本体组件的程度。", "sourceRefs": ["report:p44", "report:p47-56"] }, { "id": "metric-delivery-cost-reduction", "type": "metric", "name": "交付成本下降", "nameEn": "Delivery cost reduction", "definition": "相对从零定制，复用资产后节省的工时、上线周期和现场投入。", "sourceRefs": ["report:p16", "report:p49-56"] }, { "id": "risk-demo-trap", "type": "risk", "name": "Demo 陷阱", "nameEn": "Demo trap", "definition": "原型效果被误当成生产能力，权限、长尾、稳定性和组织采用问题没有进入验收。", "sourceRefs": ["report:p9-10", "report:p28-30"] }, { "id": "risk-outsourcing-drift", "type": "risk", "name": "外包化漂移", "nameEn": "Outsourcing drift", "definition": "团队持续响应一次性需求，却没有形成可复用资产、产品反馈和交付成本下降。", "sourceRefs": ["report:p14-17", "report:p38-40"] }, { "id": "risk-missing-sponsor", "type": "risk", "name": "缺少业务负责人", "nameEn": "Missing sponsor", "definition": "项目只有技术联系人，没有人能调整流程、协调资源或承担采用结果。", "sourceRefs": ["report:p28-30", "report:p38-39"] }, { "id": "risk-unsafe-automation", "type": "risk", "name": "不安全自动化", "nameEn": "Unsafe automation", "definition": "在高风险任务中缺少权限边界、审核、审计、回滚或人工接管。", "sourceRefs": ["report:p10", "report:p28-30"] }, { "id": "risk-weak-feedback-loop", "type": "risk", "name": "反馈链断裂", "nameEn": "Weak feedback loop", "definition": "一线问题无法进入产品与知识基线，平台也无法反向降低后续项目成本。", "sourceRefs": ["report:p14-17", "report:p22"] }, { "id": "risk-metric-theater", "type": "risk", "name": "指标表演", "nameEn": "Metric theater", "definition": "只展示模型分数、调用量或演示案例，没有业务基线、采用率和价值结果。", "sourceRefs": ["report:p29-30", "report:p58-59", "project:synthesis"] }, { "id": "risk-knowledge-fragmentation", "type": "risk", "name": "知识碎片化", "nameEn": "Knowledge fragmentation", "definition": "行业规则散落在个人、文档和项目代码中，缺少可检索、可评审、可版本化的结构。", "sourceRefs": ["report:p20-21", "report:p38"] }, { "id": "risk-overbuilt-ontology", "type": "risk", "name": "本体过度建设", "nameEn": "Overbuilt ontology", "definition": "在没有足够同类客户和复用证据时投入完整建模，维护成本超过实际收益。", "sourceRefs": ["report:p17", "report:p25", "report:p56"] }, { "id": "asset-skill", "type": "asset", "name": "Skill", "nameEn": "Skill", "definition": "封装特定任务判断、工具使用、业务规则和输出要求的可复用能力单元。", "sourceRefs": ["report:p16-17", "report:p25", "report:p79"] }, { "id": "asset-connector", "type": "asset", "name": "连接器", "nameEn": "Connector", "definition": "以稳定接口连接企业系统、数据源和协作入口，复用鉴权、映射和异常处理。", "sourceRefs": ["report:p17", "report:p25", "report:p35-36"] }, { "id": "asset-ontology", "type": "asset", "name": "业务本体", "nameEn": "Business ontology", "definition": "定义业务对象、属性、关系、动作、状态和规则的稳定语义层。", "sourceRefs": ["report:p20-21", "report:p24-26"] }, { "id": "asset-evaluation-suite", "type": "asset", "name": "评测套件", "nameEn": "Evaluation suite", "definition": "由样本、评分标准、回归检查和质量门禁组成的持续验证资产。", "sourceRefs": ["report:p4", "report:p9-10", "project:synthesis"] }, { "id": "asset-industry-template", "type": "asset", "name": "行业模板", "nameEn": "Industry template", "definition": "针对高频行业场景预置流程、角色、字段、连接器和治理要求的组合。", "sourceRefs": ["report:p4", "report:p25", "report:p36"] }, { "id": "asset-playbook", "type": "asset", "name": "交付 Playbook", "nameEn": "Delivery playbook", "definition": "记录发现、验证、上线、采用和复盘方法的可执行操作指南。", "sourceRefs": ["report:p46-56", "project:synthesis"] }, { "id": "asset-product-capability", "type": "asset", "name": "产品能力", "nameEn": "Product capability", "definition": "由多次现场需求验证后进入平台主线、可被更多客户直接使用的标准功能。", "sourceRefs": ["report:p14-17", "report:p32-36"] }, { "id": "system-agent-platform", "type": "system", "name": "Agent 平台", "nameEn": "Agent platform", "definition": "承载模型、上下文、工具、流程、运行时、评测和发布治理的开发与运行平台。", "sourceRefs": ["report:p25-26", "report:p32-36"] }, { "id": "system-enterprise-systems", "type": "system", "name": "企业业务系统", "nameEn": "Enterprise systems", "definition": "CRM、ERP、OA、知识库和行业系统等真实业务数据与动作的来源。", "sourceRefs": ["report:p8-10", "report:p20-21"] }, { "id": "system-model-layer", "type": "system", "name": "模型层", "nameEn": "Model layer", "definition": "提供生成、理解、推理和多模态能力，但不独自承担业务语义与流程责任。", "sourceRefs": ["report:p8-10", "report:p20-21"] }, { "id": "system-observability", "type": "system", "name": "可观测系统", "nameEn": "Observability system", "definition": "记录请求、工具调用、质量、成本、延迟、错误和人工接管，支持运行追踪。", "sourceRefs": ["report:p28-30", "project:synthesis"] }, { "id": "system-identity-permission", "type": "system", "name": "身份与权限系统", "nameEn": "Identity and permission system", "definition": "控制用户、Agent 和工具对数据与动作的访问范围，并提供审计依据。", "sourceRefs": ["report:p10", "report:p28-30"] }, { "id": "principle-dual-distillation", "type": "principle", "name": "双向蒸馏", "nameEn": "Bidirectional distillation", "definition": "前线把客户差异提炼为结构化反馈，平台再把共性反馈固化为标准能力并返回现场验证。", "sourceRefs": ["report:p14-17"] }, { "id": "principle-land-and-expand", "type": "principle", "name": "Land and Expand", "nameEn": "Land and expand", "definition": "先用一个高价值场景取得生产结果，再依靠采用证据、资产复用和客户信任扩展到更多流程。", "sourceRefs": ["report:p28-40"] }, { "id": "principle-self-service-end-state", "type": "principle", "name": "客户逐步自助", "nameEn": "Customer self-service end state", "definition": "成熟的 FDE 模式应降低客户对持续驻场的依赖，让客户能够基于标准资产自行扩展和运营。", "sourceRefs": ["report:p58-60"] }, { "id": "role-fdpm", "type": "role", "name": "前线部署产品经理", "nameEn": "Forward Deployed Product Manager", "definition": "负责场景取舍、价值假设、关键人协同与采用路径，与 FDE 共同把可运行结果推进到业务闭环。", "sourceRefs": ["report:p28-30"] }, { "id": "role-management", "type": "role", "name": "管理层", "nameEn": "Management", "definition": "决定组织归属、预算、内部结算和跨团队优先级，并为长期知识沉淀承担制度责任。", "sourceRefs": ["report:p42-45", "report:p47-56"] }, { "id": "role-hr", "type": "role", "name": "HR 与人才团队", "nameEn": "HR and talent team", "definition": "围绕复合能力设计招聘、项目制培养、认证与考核，避免用单一研发或销售指标评价 FDE。", "sourceRefs": ["report:p42-45", "report:p47-56"] }, { "id": "role-customer-user", "type": "role", "name": "客户一线用户", "nameEn": "Customer frontline user", "definition": "在真实流程中使用方案、暴露长尾问题并反馈采用障碍，是评测集和流程改造的重要证据来源。", "sourceRefs": ["report:p28-30", "report:p47-56"] }, { "id": "stage-cold-start", "type": "stage", "name": "冷启动", "nameEn": "Cold start", "definition": "Echo 团队从行业对象、流程和规则出发建立首版本体，同时明确首批可验证场景与扩展边界。", "sourceRefs": ["report:p47-56"] }, { "id": "stage-first-customer", "type": "stage", "name": "第一个客户", "nameEn": "First customer", "definition": "Delta 使用初版本体完成现场交付，记录缺口并通过反馈单把客户差异交回 Echo 评审。", "sourceRefs": ["report:p47-56"] }, { "id": "stage-early-reuse", "type": "stage", "name": "第二到第四个客户", "nameEn": "Early reuse", "definition": "团队开始验证同一资产在多个客户中的适用范围，并区分行业共性、客户差异和错误抽象。", "sourceRefs": ["report:p47-56"] }, { "id": "stage-scale-effect", "type": "stage", "name": "第五到第八个客户", "nameEn": "Scale effect", "definition": "可复用资产开始显著缩短交付周期，管理层据此观察边际成本、伙伴复制和资产覆盖率。", "sourceRefs": ["report:p47-56"] }, { "id": "stage-ontology-maturity", "type": "stage", "name": "本体成熟", "nameEn": "Ontology maturity", "definition": "团队从项目驱动转为产品化运营，前线主要验证例外、补充资产并帮助客户建立自助能力。", "sourceRefs": ["report:p47-60"] }, { "id": "mechanism-echo-delta-pairing", "type": "mechanism", "name": "Echo 与 Delta 配对", "nameEn": "Echo and Delta pairing", "definition": "一方维护可复用基线，一方完成现场适配，两种责任通过结构化反馈持续校准，而非彼此替代。", "sourceRefs": ["report:p14-17", "report:p47-56"] }, { "id": "mechanism-ontology-feedback-form", "type": "mechanism", "name": "本体反馈单", "nameEn": "Ontology feedback form", "definition": "用统一字段记录现场缺口、临时解法、适用范围、证据和建议归属，让经验进入可评审的资产流程。", "sourceRefs": ["report:p47-56"] }, { "id": "mechanism-internal-settlement", "type": "mechanism", "name": "内部结算", "nameEn": "Internal settlement", "definition": "通过成本抵扣或内部计价奖励高质量反馈与复用贡献，使前线团队有动力投入长期资产沉淀。", "sourceRefs": ["report:p47-56"] }, { "id": "mechanism-privacy-isolation", "type": "mechanism", "name": "数据隐私隔离", "nameEn": "Data privacy isolation", "definition": "只回流抽象后的业务模式、规则和测试结构，客户数据、身份信息与敏感实现留在授权边界内。", "sourceRefs": ["report:p47-56"] }, { "id": "mechanism-workshop-bootcamp", "type": "mechanism", "name": "工作营陪跑", "nameEn": "Workshop and bootcamp", "definition": "让客户团队围绕真实场景共同构建和验证，使能力转移、场景发现与首个可运行结果在同一过程发生。", "sourceRefs": ["report:p32-36"] }, { "id": "mechanism-partner-replication", "type": "mechanism", "name": "伙伴复制", "nameEn": "Partner replication", "definition": "原厂用标杆项目和标准资产打样，伙伴承担本地化交付，平台通过认证、评测和反馈保持质量。", "sourceRefs": ["report:p32-36", "report:p58-60"] }, { "id": "deliverable-ontology-baseline", "type": "deliverable", "name": "本体基线", "nameEn": "Ontology baseline", "definition": "描述行业对象、关系、动作、规则和扩展点的版本化基线，是后续客户适配和资产评审的共同语言。", "sourceRefs": ["report:p19-26", "report:p47-56"] }, { "id": "deliverable-ontology-feedback-record", "type": "deliverable", "name": "本体反馈记录", "nameEn": "Ontology feedback record", "definition": "记录现场证据、现有基线缺口、临时方案、建议抽象和复用范围，供 Echo 决定是否进入公共版本。", "sourceRefs": ["report:p47-56"] }, { "id": "deliverable-privacy-boundary", "type": "deliverable", "name": "隐私边界说明", "nameEn": "Privacy boundary specification", "definition": "明确哪些数据只能留在客户侧、哪些模式可以抽象回流，以及脱敏、审计和授权的责任主体。", "sourceRefs": ["report:p47-56"] }, { "id": "deliverable-settlement-ledger", "type": "deliverable", "name": "复用结算记录", "nameEn": "Reuse settlement ledger", "definition": "记录资产贡献、采用、复用收益和成本抵扣，为团队激励、预算分配与规模效应评估提供依据。", "sourceRefs": ["report:p47-56"] }, { "id": "metric-time-to-production", "type": "metric", "name": "生产上线周期", "nameEn": "Time to production", "definition": "从场景确认到受控生产可用的自然日或工作日，必须固定起点、终点、排除项和统计窗口。", "sourceRefs": ["report:p28-30", "report:p58-60", "project:synthesis"] }, { "id": "metric-asset-coverage", "type": "metric", "name": "资产覆盖率", "nameEn": "Asset coverage", "definition": "可由标准资产直接覆盖的交付任务数除以同类交付任务总数，用于观察本体和 Skill 的成熟度。", "sourceRefs": ["report:p47-56", "project:synthesis"] }, { "id": "metric-marginal-delivery-cost", "type": "metric", "name": "边际交付成本", "nameEn": "Marginal delivery cost", "definition": "新增同类客户所需的人天、云资源和支持成本，用来验证沉淀资产是否真正产生规模效应。", "sourceRefs": ["report:p14-17", "report:p47-56"] }, { "id": "metric-customer-self-service", "type": "metric", "name": "客户自助率", "nameEn": "Customer self-service rate", "definition": "由客户独立完成并达到验收标准的扩展任务数除以全部扩展任务数，反映能力转移效果。", "sourceRefs": ["report:p58-60", "project:synthesis"] }, { "id": "risk-missing-ontology-layer", "type": "risk", "name": "本体层缺失", "nameEn": "Missing ontology layer", "definition": "业务对象、流程和规则没有统一表达时，项目反复从需求澄清和接口适配开始，经验无法复用。", "sourceRefs": ["report:p19-26", "report:p28-40"] }, { "id": "risk-organizational-misalignment", "type": "risk", "name": "组织错配", "nameEn": "Organizational misalignment", "definition": "FDE 被单纯放入销售、外包或成本中心时，短期项目收入会压过产品反馈、客户采用和知识沉淀。", "sourceRefs": ["report:p28-45"] }, { "id": "risk-margin-pressure", "type": "risk", "name": "利润率压力", "nameEn": "Margin pressure", "definition": "高密度专家投入若没有复用率提升和伙伴复制，会让每个新增客户都重复消耗相同交付成本。", "sourceRefs": ["report:p28-40"] }, { "id": "risk-partner-quality", "type": "risk", "name": "伙伴交付质量", "nameEn": "Partner delivery quality", "definition": "生态扩张缺少认证、评测和反馈约束时，交付标准会分化，现场问题也难以回流平台。", "sourceRefs": ["report:p32-36", "report:p58-60"] }, { "id": "risk-data-privacy-leak", "type": "risk", "name": "客户数据外溢", "nameEn": "Customer data leakage", "definition": "沉淀资产时若把客户原始数据、身份信息或专属逻辑带入公共版本，会破坏授权边界与客户信任。", "sourceRefs": ["report:p47-56"] }, { "id": "risk-stale-market-claim", "type": "risk", "name": "市场信息过期", "nameEn": "Stale market claim", "definition": "招聘数量、薪酬、产品能力和组织结构会持续变化，报告样本只能作为历史观察而非当前事实。", "sourceRefs": ["report:p61-79", "needs-verification"] }, { "id": "asset-semantic-model", "type": "asset", "name": "业务语义模型", "nameEn": "Business semantic model", "definition": "用对象、关系、动作和规则表达业务世界，为模型、应用和系统连接提供统一的可执行语义。", "sourceRefs": ["report:p19-26"] }, { "id": "asset-feedback-template", "type": "asset", "name": "反馈单模板", "nameEn": "Feedback template", "definition": "把前线经验转成固定字段和评审入口，减少依赖口头复盘并支持跨项目比较和版本管理。", "sourceRefs": ["report:p47-56"] }, { "id": "asset-training-certification", "type": "asset", "name": "项目制培训与认证", "nameEn": "Project training and certification", "definition": "围绕真实项目、角色能力和交付证据设计训练与认证，避免只用课堂考试判断前线能力。", "sourceRefs": ["report:p42-45"] }, { "id": "system-data-layer", "type": "system", "name": "数据层", "nameEn": "Data layer", "definition": "承载业务事实、历史记录和实时状态，为本体对象和上层应用提供可治理的数据来源。", "sourceRefs": ["report:p19-26"] }, { "id": "system-ontology-layer", "type": "system", "name": "本体层", "nameEn": "Ontology layer", "definition": "把底层数据映射为业务对象、关系、动作和约束，连接客户语言、应用逻辑与模型能力。", "sourceRefs": ["report:p19-26"] }, { "id": "system-application-layer", "type": "system", "name": "应用层", "nameEn": "Application layer", "definition": "面向具体用户和任务提供工作流、界面与自动化能力，并通过本体层读写业务对象和动作。", "sourceRefs": ["report:p19-26"] }, { "id": "system-ai-tool-layer", "type": "system", "name": "AI 工具层", "nameEn": "AI tool layer", "definition": "通过 AI 编程、办公助手和 Agent 工具降低原型、接口适配、测试与文档等工程执行成本。", "sourceRefs": ["report:p19-26", "report:p32-36"] }, { "id": "market-overseas-fde-2026", "type": "market", "name": "海外 FDE 招聘市场", "nameEn": "Overseas FDE market", "definition": "报告采集的海外 FDE 与相邻岗位样本，反映 2026 年 4-7 月的岗位命名、能力要求和薪酬披露情况。", "sourceRefs": ["report:p64-79", "needs-verification"] }, { "id": "market-china-fde-2026", "type": "market", "name": "中国 FDE 招聘市场", "nameEn": "China FDE market", "definition": "国内云厂商、模型公司和平台企业发布的 FDE 及相邻客户工程岗位，名称与薪酬口径仍较分散。", "sourceRefs": ["report:p73-79", "needs-verification"] }, { "id": "job-profile-fde-core", "type": "job-profile", "name": "FDE 核心岗位画像", "nameEn": "Core FDE job profile", "definition": "兼具客户业务拆解、全栈实现、系统集成、生产治理与资产回流责任的复合型客户工程岗位。", "sourceRefs": ["report:p64-79", "needs-verification"] }, { "id": "compensation-overseas-fde-2026", "type": "compensation", "name": "海外 FDE 薪酬样本", "nameEn": "Overseas FDE compensation sample", "definition": "以 USD 年基薪为主的公开招聘样本，奖金、股权和福利需要单独核验，不能直接视为总包。", "sourceRefs": ["report:p67-68", "needs-verification"] }, { "id": "compensation-china-fde-tiers-2026", "type": "compensation", "name": "国内 FDE 薪酬分层样本", "nameEn": "China FDE compensation tiers", "definition": "以 CNY 月薪和发薪月数表达的国内招聘样本分层，职级、奖金、股权和补贴不在统一口径内。", "sourceRefs": ["report:p73-76", "needs-verification"] } ], "relations": [ {"from": "role-fde", "to": "principle-frontline-learning", "type": "owns"}, {"from": "role-echo", "to": "capability-knowledge-modeling", "type": "owns"}, {"from": "role-echo", "to": "capability-asset-productization", "type": "owns"}, {"from": "role-delta", "to": "capability-full-stack-delivery", "type": "owns"}, {"from": "role-delta", "to": "capability-system-integration", "type": "owns"}, {"from": "role-customer-sponsor", "to": "capability-change-management", "type": "owns"}, {"from": "role-platform-team", "to": "asset-product-capability", "type": "owns"}, {"from": "role-ecosystem-partner", "to": "stage-reuse", "type": "owns"}, {"from": "stage-discovery", "to": "stage-runnable-demo", "type": "precedes"}, {"from": "stage-runnable-demo", "to": "stage-pilot", "type": "precedes"}, {"from": "stage-pilot", "to": "stage-production", "type": "precedes"}, {"from": "stage-production", "to": "stage-adoption", "type": "precedes"}, {"from": "stage-adoption", "to": "stage-reuse", "type": "precedes"}, {"from": "stage-discovery", "to": "deliverable-scenario-map", "type": "produces"}, {"from": "stage-runnable-demo", "to": "deliverable-runnable-demo", "type": "produces"}, {"from": "stage-pilot", "to": "deliverable-evaluation-set", "type": "produces"}, {"from": "stage-production", "to": "deliverable-production-solution", "type": "produces"}, {"from": "stage-production", "to": "deliverable-runbook", "type": "produces"}, {"from": "stage-adoption", "to": "deliverable-adoption-plan", "type": "produces"}, {"from": "stage-adoption", "to": "deliverable-value-review", "type": "produces"}, {"from": "stage-reuse", "to": "deliverable-reusable-asset", "type": "produces"}, {"from": "deliverable-reusable-asset", "to": "asset-skill", "type": "enables"}, {"from": "deliverable-reusable-asset", "to": "asset-connector", "type": "enables"}, {"from": "deliverable-reusable-asset", "to": "asset-ontology", "type": "enables"}, {"from": "deliverable-reusable-asset", "to": "asset-evaluation-suite", "type": "enables"}, {"from": "deliverable-reusable-asset", "to": "asset-industry-template", "type": "enables"}, {"from": "deliverable-reusable-asset", "to": "asset-playbook", "type": "enables"}, {"from": "deliverable-reusable-asset", "to": "asset-product-capability", "type": "enables"}, {"from": "asset-skill", "to": "stage-reuse", "type": "reused_in"}, {"from": "asset-connector", "to": "stage-reuse", "type": "reused_in"}, {"from": "asset-ontology", "to": "stage-reuse", "type": "reused_in"}, {"from": "asset-evaluation-suite", "to": "stage-reuse", "type": "reused_in"}, {"from": "asset-industry-template", "to": "stage-reuse", "type": "reused_in"}, {"from": "asset-playbook", "to": "stage-reuse", "type": "reused_in"}, {"from": "capability-business-discovery", "to": "deliverable-scenario-map", "type": "produces"}, {"from": "capability-full-stack-delivery", "to": "deliverable-runnable-demo", "type": "produces"}, {"from": "capability-evaluation", "to": "deliverable-evaluation-set", "type": "produces"}, {"from": "capability-production-governance", "to": "deliverable-runbook", "type": "produces"}, {"from": "capability-change-management", "to": "deliverable-adoption-plan", "type": "produces"}, {"from": "capability-asset-productization", "to": "deliverable-reusable-asset", "type": "produces"}, {"from": "deliverable-value-review", "to": "metric-adoption-rate", "type": "measured_by"}, {"from": "deliverable-value-review", "to": "metric-task-success-rate", "type": "measured_by"}, {"from": "deliverable-value-review", "to": "metric-cycle-time", "type": "measured_by"}, {"from": "deliverable-value-review", "to": "metric-expansion-rate", "type": "measured_by"}, {"from": "deliverable-production-solution", "to": "metric-production-reliability", "type": "measured_by"}, {"from": "deliverable-production-solution", "to": "metric-human-review-rate", "type": "measured_by"}, {"from": "stage-reuse", "to": "metric-reuse-rate", "type": "measured_by"}, {"from": "stage-reuse", "to": "metric-delivery-cost-reduction", "type": "measured_by"}, {"from": "principle-80-95-99", "to": "risk-demo-trap", "type": "mitigates"}, {"from": "principle-sedimentation-first", "to": "risk-outsourcing-drift", "type": "mitigates"}, {"from": "principle-human-fallback", "to": "risk-unsafe-automation", "type": "mitigates"}, {"from": "principle-frontline-learning", "to": "risk-weak-feedback-loop", "type": "mitigates"}, {"from": "principle-value-before-model", "to": "risk-metric-theater", "type": "mitigates"}, {"from": "capability-change-management", "to": "risk-missing-sponsor", "type": "mitigates"}, {"from": "capability-knowledge-modeling", "to": "risk-knowledge-fragmentation", "type": "mitigates"}, {"from": "metric-reuse-rate", "to": "risk-overbuilt-ontology", "type": "mitigates"}, {"from": "capability-agent-engineering", "to": "system-agent-platform", "type": "depends_on"}, {"from": "capability-system-integration", "to": "system-enterprise-systems", "type": "depends_on"}, {"from": "capability-agent-engineering", "to": "system-model-layer", "type": "depends_on"}, {"from": "capability-production-governance", "to": "system-observability", "type": "depends_on"}, {"from": "capability-production-governance", "to": "system-identity-permission", "type": "depends_on"}, {"from": "asset-skill", "to": "system-agent-platform", "type": "depends_on"}, {"from": "asset-connector", "to": "system-enterprise-systems", "type": "depends_on"}, {"from": "asset-ontology", "to": "system-enterprise-systems", "type": "depends_on"}, {"from": "role-delta", "to": "role-echo", "type": "feeds_back_to"}, {"from": "role-echo", "to": "role-platform-team", "type": "feeds_back_to"}, {"from": "role-platform-team", "to": "role-delta", "type": "feeds_back_to"}, {"from": "metric-task-success-rate", "to": "capability-evaluation", "type": "feeds_back_to"}, {"from": "metric-adoption-rate", "to": "capability-change-management", "type": "feeds_back_to"}, {"from": "metric-reuse-rate", "to": "capability-asset-productization", "type": "feeds_back_to"}, {"from": "principle-human-fallback", "to": "system-identity-permission", "type": "governs"}, {"from": "principle-value-before-model", "to": "stage-discovery", "type": "governs"}, {"from": "principle-sedimentation-first", "to": "stage-reuse", "type": "governs"}, {"from": "principle-three-party-loop", "to": "role-ecosystem-partner", "type": "governs"}, {"from": "role-fdpm", "to": "capability-business-discovery", "type": "owns"}, {"from": "role-fdpm", "to": "capability-change-management", "type": "owns"}, {"from": "role-management", "to": "mechanism-internal-settlement", "type": "owns"}, {"from": "role-hr", "to": "asset-training-certification", "type": "owns"}, {"from": "role-customer-user", "to": "deliverable-evaluation-set", "type": "feeds_back_to"}, {"from": "role-delta", "to": "mechanism-ontology-feedback-form", "type": "owns"}, {"from": "role-echo", "to": "deliverable-ontology-baseline", "type": "owns"}, {"from": "role-ecosystem-partner", "to": "mechanism-partner-replication", "type": "owns"}, {"from": "stage-cold-start", "to": "stage-first-customer", "type": "precedes"}, {"from": "stage-first-customer", "to": "stage-early-reuse", "type": "precedes"}, {"from": "stage-early-reuse", "to": "stage-scale-effect", "type": "precedes"}, {"from": "stage-scale-effect", "to": "stage-ontology-maturity", "type": "precedes"}, {"from": "stage-cold-start", "to": "deliverable-ontology-baseline", "type": "produces"}, {"from": "stage-first-customer", "to": "deliverable-ontology-feedback-record", "type": "produces"}, {"from": "stage-early-reuse", "to": "asset-feedback-template", "type": "produces"}, {"from": "stage-scale-effect", "to": "deliverable-settlement-ledger", "type": "produces"}, {"from": "stage-ontology-maturity", "to": "asset-industry-template", "type": "produces"}, {"from": "stage-ontology-maturity", "to": "metric-customer-self-service", "type": "measured_by"}, {"from": "principle-dual-distillation", "to": "mechanism-echo-delta-pairing", "type": "governs"}, {"from": "principle-land-and-expand", "to": "stage-runnable-demo", "type": "governs"}, {"from": "principle-land-and-expand", "to": "metric-expansion-rate", "type": "measured_by"}, {"from": "principle-self-service-end-state", "to": "metric-customer-self-service", "type": "measured_by"}, {"from": "principle-self-service-end-state", "to": "stage-ontology-maturity", "type": "governs"}, {"from": "mechanism-echo-delta-pairing", "to": "principle-dual-distillation", "type": "enables"}, {"from": "mechanism-ontology-feedback-form", "to": "deliverable-ontology-feedback-record", "type": "produces"}, {"from": "deliverable-ontology-feedback-record", "to": "role-echo", "type": "feeds_back_to"}, {"from": "mechanism-internal-settlement", "to": "risk-weak-feedback-loop", "type": "mitigates"}, {"from": "mechanism-internal-settlement", "to": "deliverable-settlement-ledger", "type": "produces"}, {"from": "mechanism-privacy-isolation", "to": "risk-data-privacy-leak", "type": "mitigates"}, {"from": "mechanism-privacy-isolation", "to": "deliverable-privacy-boundary", "type": "produces"}, {"from": "mechanism-workshop-bootcamp", "to": "stage-adoption", "type": "enables"}, {"from": "mechanism-workshop-bootcamp", "to": "asset-training-certification", "type": "produces"}, {"from": "mechanism-partner-replication", "to": "stage-reuse", "type": "enables"}, {"from": "mechanism-partner-replication", "to": "risk-partner-quality", "type": "mitigates"}, {"from": "deliverable-ontology-baseline", "to": "asset-semantic-model", "type": "enables"}, {"from": "asset-semantic-model", "to": "system-ontology-layer", "type": "reused_in"}, {"from": "asset-feedback-template", "to": "mechanism-ontology-feedback-form", "type": "reused_in"}, {"from": "deliverable-privacy-boundary", "to": "system-identity-permission", "type": "governs"}, {"from": "stage-production", "to": "metric-time-to-production", "type": "measured_by"}, {"from": "stage-reuse", "to": "metric-asset-coverage", "type": "measured_by"}, {"from": "stage-scale-effect", "to": "metric-marginal-delivery-cost", "type": "measured_by"}, {"from": "metric-asset-coverage", "to": "risk-missing-ontology-layer", "type": "mitigates"}, {"from": "metric-marginal-delivery-cost", "to": "risk-margin-pressure", "type": "mitigates"}, {"from": "system-data-layer", "to": "system-ontology-layer", "type": "enables"}, {"from": "system-ontology-layer", "to": "system-application-layer", "type": "enables"}, {"from": "system-model-layer", "to": "system-application-layer", "type": "enables"}, {"from": "system-ai-tool-layer", "to": "capability-full-stack-delivery", "type": "enables"}, {"from": "asset-skill", "to": "system-ontology-layer", "type": "depends_on"}, {"from": "asset-connector", "to": "system-data-layer", "type": "depends_on"}, {"from": "capability-knowledge-modeling", "to": "risk-missing-ontology-layer", "type": "mitigates"}, {"from": "principle-sedimentation-first", "to": "risk-margin-pressure", "type": "mitigates"}, {"from": "principle-three-party-loop", "to": "mechanism-partner-replication", "type": "governs"}, {"from": "mechanism-echo-delta-pairing", "to": "risk-organizational-misalignment", "type": "mitigates"}, {"from": "deliverable-value-review", "to": "risk-stale-market-claim", "type": "mitigates"}, {"from": "job-profile-fde-core", "to": "role-fde", "type": "observed_in"}, {"from": "job-profile-fde-core", "to": "capability-full-stack-delivery", "type": "requires"}, {"from": "job-profile-fde-core", "to": "capability-business-discovery", "type": "requires"}, {"from": "job-profile-fde-core", "to": "market-overseas-fde-2026", "type": "observed_in"}, {"from": "job-profile-fde-core", "to": "market-china-fde-2026", "type": "observed_in"}, {"from": "compensation-overseas-fde-2026", "to": "market-overseas-fde-2026", "type": "observed_in"}, {"from": "compensation-china-fde-tiers-2026", "to": "market-china-fde-2026", "type": "observed_in"}, {"from": "compensation-overseas-fde-2026", "to": "compensation-china-fde-tiers-2026", "type": "compared_with"}, {"from": "compensation-overseas-fde-2026", "to": "risk-stale-market-claim", "type": "depends_on"}, {"from": "compensation-china-fde-tiers-2026", "to": "risk-stale-market-claim", "type": "depends_on"} ] }