[{"data":1,"prerenderedAt":299},["ShallowReactive",2],{"docs-doc-\u002Fdocs\u002Fmechanism\u002Fai-employee-task":3,"docs-live-paths":248},{"id":4,"title":5,"body":6,"description":234,"extension":235,"meta":236,"navigation":243,"path":244,"seo":245,"stem":246,"__hash__":247},"content\u002Fdocs\u002Fmechanism\u002Fai-employee-task.md","AI 数字员工的一次完整任务：从派发到交付",{"type":7,"value":8,"toc":223},"minimark",[9,27,31,38,43,46,50,53,75,84,88,91,110,114,121,141,148,152,155,175,180,183,189,195,201,204],[10,11,12],"blockquote",{},[13,14,15,16,20,21,26],"p",{},"本文解决什么问题：介绍员工体系时大家常问「AI 会不会乱来、怎么知道它干到哪一步了」。这篇讲一个任务从",[17,18,19],"strong",{},"下达 → 执行 → 人审 → 交付","完整走一遍时的机制：谁批准关键步骤、越权怎么被拦、结果为什么可追溯。认识层面的清单见",[22,23,25],"a",{"href":24},"\u002Fdocs\u002Fconcepts\u002Fai-team","AI 数字员工体系","，这篇讲链路本身。",[28,29,30],"h2",{"id":30},"一句话机制",[13,32,33,34,37],{},"AI 数字员工不是一个「随便聊」的助手，而是",[17,35,36],{},"带着明确任务、在授权边界内执行、关键步骤等您拍板","的一整套机制。一次任务的生命周期大致是：",[13,39,40],{},[17,41,42],{},"派发 → 确认边界 → 执行 → （需要时）人审 → 交付并留痕 → 您可回看",[13,44,45],{},"每一个环节都对应一个「这是平台能力在做、而不是 AI 自己说了算」的控制点。",[28,47,49],{"id":48},"派发怎么把活交给它","① 派发：怎么把活交给它",[13,51,52],{},"有三种常见方式把一件事交给员工：",[54,55,56,63,69],"ul",{},[57,58,59,62],"li",{},[17,60,61],{},"对话里直接说","——例如「帮我建一个客户表」，员工确认任务范围后开始；",[57,64,65,68],{},[17,66,67],{},"结构化表单","——把要求逐项填清楚后派发，适合边界明确的批量任务；",[57,70,71,74],{},[17,72,73],{},"员工卡片\u002F例行班表","——需要周期性重复的活（如每周一自动出一份经营周报），提前配成定时任务，到期自动执行，不必每次手动喊它。",[10,76,77],{},[13,78,79,80,83],{},"无论哪种方式，第一步都是",[17,81,82],{},"确认边界","：员工会按平台配置的职责与可读资料范围判断自己能不能做、做到什么程度——超出能力或权限范围的事，它不会硬做。",[28,85,87],{"id":86},"执行按授权与规则来","② 执行：按授权与规则来",[13,89,90],{},"执行阶段 AI 不是「自由发挥」，而是受两套约束夹着走：",[54,92,93,104],{},[57,94,95,98,99,103],{},[17,96,97],{},"权限约束","：AI 与人在同一套权限体系下行动——它只能读被授权范围内的数据、只能碰被允许调用的能力。这与",[22,100,102],{"href":101},"\u002Fdocs\u002Fmechanism\u002Fpermission","权限体系","是同一把尺子，不是给 AI 开了特权后门。",[57,105,106,109],{},[17,107,108],{},"规则约束","：涉及可重复、规则明确的活（查数、汇总、拟稿、按模板生成内容），由它自动执行；越权请求在请求层就被拒绝。",[28,111,113],{"id":112},"人审哪些操作-ai-不拥有最终拍板权","③ 人审：哪些操作 AI 不拥有「最终拍板权」",[13,115,116,117,120],{},"这是整个机制里最关键的信任点——",[17,118,119],{},"并非所有事 AI 都能自己完成","。以下类型会被拦下来，停在「待审批」，等负责人确认后才继续：",[54,122,123,129,135],{},[57,124,125,128],{},[17,126,127],{},"发布类操作","（如把模型\u002F页面发布上线）；",[57,130,131,134],{},[17,132,133],{},"数据写入 \u002F 不可逆操作","；",[57,136,137,140],{},[17,138,139],{},"对外交付的内容","（正式发给客户\u002F同事的东西）。",[13,142,143,144,147],{},"审批是「人拍板、AI 执行」：AI 把结果准备好、呈给该审批的人，通过后落地，不通过则不会擅自继续。也就是说——",[17,145,146],{},"平台里 AI 不拥有最终拍板权","，涉及决策和不可逆动作的地方，回到人。",[28,149,151],{"id":150},"交付与留痕为什么结果可回看","④ 交付与留痕：为什么结果可回看",[13,153,154],{},"任务交付后，不是「干完就消失」：",[54,156,157,163,169],{},[57,158,159,162],{},[17,160,161],{},"工作日志","：每个员工按时间线记录执行了什么、交付了什么——您打开员工档案就能回看一段历史；",[57,164,165,168],{},[17,166,167],{},"审批记录","：谁在何时审了什么，留痕可追溯；",[57,170,171,174],{},[17,172,173],{},"运营中心","：需要看全局时，管理者可查看整批员工的状态灯、待审批队列与运行情况，而不是逐个去翻。",[10,176,177],{},[13,178,179],{},"信任的来源不是「AI 很可靠」，而是「AI 每一步都能被看见、被回溯、关键处被您把关」。",[28,181,182],{"id":182},"常见疑问",[13,184,185,188],{},[17,186,187],{},"AI 会自己决定做超出授权的事吗？","\n不会。它只在被授权的数据与能力范围内行动，越权请求会被拒绝——这是机制层约束，不是靠自觉。",[13,190,191,194],{},[17,192,193],{},"所有任务都要人审吗？","\n不是。只有涉及发布、数据写入、不可逆操作、对外交付的关键环节需要审批；纯只读的分析、汇总类任务可以自动完成。哪些操作要人审，由员工配置定义。",[13,196,197,200],{},[17,198,199],{},"任务执行到一半，我能看到进度吗？","\n可以。员工状态与进度在界面可见，异常与待审事项会有提示——它干到哪一步、卡在哪，是透明的。",[28,202,203],{"id":203},"相关阅读",[54,205,206,211,218],{},[57,207,208,209],{},"有哪些员工、怎么查看与使用 → ",[22,210,25],{"href":24},[57,212,213,214],{},"AI 的工作机制与能力边界 → ",[22,215,217],{"href":216},"\u002Fdocs\u002Fconcepts\u002Fai","AI 数字员工 · 工作机制",[57,219,220,221],{},"AI 与人的权限同一套口径 → ",[22,222,102],{"href":101},{"title":224,"searchDepth":225,"depth":225,"links":226},"",2,[227,228,229,230,231,232,233],{"id":30,"depth":225,"text":30},{"id":48,"depth":225,"text":49},{"id":86,"depth":225,"text":87},{"id":112,"depth":225,"text":113},{"id":150,"depth":225,"text":151},{"id":182,"depth":225,"text":182},{"id":203,"depth":225,"text":203},"一个任务从下达到交付要经过哪些环节、哪些操作必须人审批、全程如何留痕——AI 数字员工「按规矩干活」的端到端机制。","md",{"audience":237,"type":238,"section":239,"pr_order":240,"role":241,"duration":242},"public","mechanism","框架机制与边界",4,"老板 \u002F 实施搭建者 \u002F 系统管理员","约 5 分钟",true,"\u002Fdocs\u002Fmechanism\u002Fai-employee-task",{"title":5,"description":234},"docs\u002Fmechanism\u002Fai-employee-task","odfbCQxzAQ1gqxPZCuM0ANeIj0GMd-tOqJu-TLQDNP8",[249,250,251,253,255,257,259,261,263,265,267,269,271,273,275,277,279,281,283,284,286,288,289,291,293,295,297],{"path":216},{"path":24},{"path":252},"\u002Fdocs\u002Fconcepts\u002Fcore",{"path":254},"\u002Fdocs\u002Fconcepts\u002Fflux",{"path":256},"\u002Fdocs\u002Fconcepts\u002Fmetrics",{"path":258},"\u002Fdocs\u002Fconcepts\u002Fview",{"path":260},"\u002Fdocs\u002Fdemo-center",{"path":262},"\u002Fdocs\u002Fdeploy\u002Foverview",{"path":264},"\u002Fdocs\u002Ffaq",{"path":266},"\u002Fdocs\u002Fglossary",{"path":268},"\u002Fdocs\u002Fguide\u002Fai-kb",{"path":270},"\u002Fdocs\u002Fguide\u002Fcrud",{"path":272},"\u002Fdocs\u002Fguide\u002Fdb-connect",{"path":274},"\u002Fdocs\u002Fguide\u002Fmodel-gen",{"path":276},"\u002Fdocs\u002Fintro\u002Fframeworks",{"path":278},"\u002Fdocs\u002Fintro\u002Foverview",{"path":280},"\u002Fdocs\u002Fintro\u002Fvalue",{"path":282},"\u002Fdocs\u002Fintro\u002Fwhy",{"path":244},{"path":285},"\u002Fdocs\u002Fmechanism\u002Fdata-flux",{"path":287},"\u002Fdocs\u002Fmechanism\u002Fmetrics-contract",{"path":101},{"path":290},"\u002Fdocs\u002Fmechanism\u002Fpublish",{"path":292},"\u002Fdocs\u002Fquickstart\u002Fclone-template",{"path":294},"\u002Fdocs\u002Fquickstart\u002Fdemo-30s",{"path":296},"\u002Fdocs\u002Fquickstart\u002Ffive-minutes",{"path":298},"\u002Fdocs\u002Fsystem\u002Foverview",1788586879703]