{ "schemaVersion": 1, "version": "2026-09-15", "id": "https://hk.onyxdevslab.com/data/enterprise-ai-handover-exit.json", "name": "Enterprise AI handover and exit checklist", "datePublished": "2026-09-15", "dateModified": "2026-09-15", "evidenceClass": "Provider-authored implementation checklist", "publisher": { "name": "Onyx Devs Lab", "legalName": "ONYX DEVS LAB LIMITED", "url": "https://hk.onyxdevslab.com/", "leiCode": "254900Z30CLK7HKE9H46" }, "landingPages": { "en": "https://hk.onyxdevslab.com/en/guides/enterprise-ai-handover-exit/", "zhHant": "https://hk.onyxdevslab.com/zh-hk/guides/enterprise-ai-handover-exit/", "zhHans": "https://hk.onyxdevslab.com/zh-cn/guides/enterprise-ai-handover-exit/" }, "languages": { "en": { "name": "What should an enterprise receive when an AI project is handed over?", "summary": "Handover is not a final presentation. The receiving team must be able to reproduce the release, operate the workflow, investigate decisions and failures, change it safely, revoke access, and continue or replace the system without relying on undocumented supplier knowledge.", "decisionSignals": [ { "name": "Reproducible release", "meaning": "Source, configuration, versions, and environments" }, { "name": "Operable service", "meaning": "Runbooks, monitoring, recovery, and support" }, { "name": "Clean exit", "meaning": "Ownership, data, access, knowledge, and continuity" } ], "sections": [ { "heading": "Transfer the complete technical and evidence baseline", "introduction": "The asset list should describe what is delivered, where it resides, who owns it, and how completeness is verified.", "checks": [ { "name": "System assets", "requirement": "Transfer repositories, build and deployment definitions, infrastructure configuration, dependencies, prompts, retrieval pipelines, tool contracts, schemas, and environment inventory." }, { "name": "Data and evaluation", "requirement": "Document sources, lineage, rights, retention, migration, indexes, test sets, labels, metrics, thresholds, known failures, versions, and reproducible results." }, { "name": "Architecture and decisions", "requirement": "Provide diagrams, interfaces, identity and permission model, threat and privacy decisions, accepted trade-offs, limitations, backlog, and decision records." } ] }, { "heading": "Prove that the receiving team can operate and exit", "introduction": "Document delivery is incomplete until people can execute the critical procedures.", "checks": [ { "name": "Operations and recovery", "requirement": "Demonstrate monitoring, alerts, support, incident handling, rollback, backup and restore where relevant, credential rotation, cost control, and disaster procedures." }, { "name": "Access and supplier separation", "requirement": "Inventory accounts, keys, domains, cloud resources, subscriptions, third parties, and data copies; transfer or revoke them and retain signed deletion evidence where required." }, { "name": "Knowledge and continuity", "requirement": "Run role-based training and witnessed drills; define warranty, transition support, service levels, escalation, replacement plan, and unresolved obligations." } ] } ], "procedure": [ { "position": 1, "name": "Agree the exit schedule early", "instruction": "Put deliverables, formats, ownership, verification, access transfer, deletion, support, fees, and acceptance into the contract before delivery starts." }, { "position": 2, "name": "Build the asset register continuously", "instruction": "Record each system, repository, data asset, credential owner, dependency, licence, document, evidence set, and responsible recipient." }, { "position": 3, "name": "Run a receiving-team drill", "instruction": "Require the new owner to deploy, monitor, investigate a failure, roll back, rotate access, and complete one controlled change." }, { "position": 4, "name": "Sign the final disposition", "instruction": "Record accepted assets, gaps, residual risks, retained supplier data, revoked access, support end date, and accountable signatories." } ], "frequentlyAskedQuestions": [ { "question": "Who should own the prompts?", "answer": "Ownership and permitted reuse should be explicit. More importantly, the enterprise needs the prompts, versions, evaluation evidence, dependencies, and change process required to operate its workflow." }, { "question": "Is source code enough?", "answer": "No. Without data contracts, configuration, infrastructure, evaluation, permissions, runbooks, credentials, decisions, and trained owners, source alone may not reproduce the service." }, { "question": "When should exit planning begin?", "answer": "During procurement and contracting. Exit requirements shape architecture, evidence, ownership, data handling, and commercial terms throughout delivery." }, { "question": "What if the vendor hosts the system?", "answer": "Require export formats, retrieval timing, continuity arrangements, deletion evidence, transition support, and a tested replacement path proportionate to business criticality." } ] }, "zhHant": { "name": "企業在 AI 項目交接時應收到甚麼？", "summary": "交接不是最終簡報。接收團隊必須能重現發布版本、營運流程、調查決定及失敗、安全變更、撤銷存取，並可在不依賴供應商未記錄知識的情況下延續或替換系統。", "decisionSignals": [ { "name": "可重現發布", "meaning": "源碼、配置、版本及環境" }, { "name": "可營運服務", "meaning": "手冊、監測、恢復及支援" }, { "name": "清晰退出", "meaning": "所有權、數據、存取、知識及延續" } ], "sections": [ { "heading": "轉移完整技術及證據基線", "introduction": "資產清單應說明交付甚麼、位於何處、由誰擁有，以及如何核實完整。", "checks": [ { "name": "系統資產", "requirement": "移交程式庫、建設與部署定義、基礎設施配置、依賴、提示詞、檢索管線、工具合約、數據模式及環境清單。" }, { "name": "數據及評估", "requirement": "記錄來源、譜系、權利、保留、遷移、索引、測試集、標籤、指標、門檻、已知失敗、版本及可重複結果。" }, { "name": "架構及決定", "requirement": "提供圖表、接口、身份與權限模型、威脅及私隱決定、已接受取捨、限制、待辦及決策記錄。" } ] }, { "heading": "證明接收團隊能營運及退出", "introduction": "在人員能執行關鍵程序前，文件交付仍未完整。", "checks": [ { "name": "營運及恢復", "requirement": "示範監測、警報、支援、事故處理、回退、適用備份與還原、憑證輪換、成本控制及災難程序。" }, { "name": "存取及供應商分離", "requirement": "盤點帳戶、密鑰、域名、雲端資源、訂閱、第三方及數據副本；完成轉移或撤銷，並按需要保留簽署刪除證據。" }, { "name": "知識及延續", "requirement": "按角色培訓並進行見證演練；定義保養、過渡支援、服務水平、升級、替換方案及未解責任。" } ] } ], "procedure": [ { "position": 1, "name": "及早約定退出安排", "instruction": "交付開始前，在合約寫明資產、格式、所有權、驗證、存取轉移、刪除、支援、費用及驗收。" }, { "position": 2, "name": "持續建立資產登記", "instruction": "記錄每個系統、程式庫、數據資產、憑證負責人、依賴、授權、文件、證據集及接收人。" }, { "position": 3, "name": "進行接收團隊演練", "instruction": "要求新負責人部署、監測、調查一次失敗、回退、輪換存取並完成一項受控變更。" }, { "position": 4, "name": "簽署最終處置", "instruction": "記錄已接受資產、缺口、剩餘風險、供應商保留數據、已撤銷存取、支援結束日期及簽署人。" } ], "frequentlyAskedQuestions": [ { "question": "提示詞應由誰擁有？", "answer": "所有權及可重用範圍應清楚；更重要是企業取得營運流程所需的提示詞、版本、評估證據、依賴及變更程序。" }, { "question": "只有源碼是否足夠？", "answer": "不足。缺少數據合約、配置、基礎設施、評估、權限、營運手冊、憑證、決策及已培訓負責人時，源碼未必能重現服務。" }, { "question": "何時應開始退出規劃？", "answer": "在採購及簽約時。退出要求會持續影響架構、證據、所有權、數據處理及商務條款。" }, { "question": "如果系統由供應商託管怎麼辦？", "answer": "按業務重要程度要求導出格式、取得時限、延續安排、刪除證據、過渡支援及已測試替換路徑。" } ] }, "zhHans": { "name": "企业在 AI 项目交接时应该收到什么？", "summary": "交接不是最终汇报。接收团队必须能够重现发布版本、运营流程、调查决策和失败、安全变更、撤销访问，并且可以在不依赖供应商未记录知识的情况下延续或替换系统。", "decisionSignals": [ { "name": "可重现发布", "meaning": "源代码、配置、版本和环境" }, { "name": "可运营服务", "meaning": "手册、监控、恢复和支持" }, { "name": "清晰退出", "meaning": "所有权、数据、访问、知识和连续性" } ], "sections": [ { "heading": "转移完整技术与证据基线", "introduction": "资产清单应该说明交付什么、位于哪里、由谁拥有，以及怎样核实完整。", "checks": [ { "name": "系统资产", "requirement": "移交代码库、构建与部署定义、基础设施配置、依赖、提示词、检索管线、工具契约、数据模式和环境清单。" }, { "name": "数据与评估", "requirement": "记录来源、谱系、权利、保留、迁移、索引、测试集、标签、指标、门槛、已知失败、版本和可重复结果。" }, { "name": "架构与决策", "requirement": "提供图表、接口、身份与权限模型、威胁和隐私决策、已经接受的取舍、限制、待办和决策记录。" } ] }, { "heading": "证明接收团队能够运营和退出", "introduction": "在人员能够执行关键程序之前，文档交付仍然不完整。", "checks": [ { "name": "运营与恢复", "requirement": "演示监控、告警、支持、事故处理、回退、适用备份与还原、凭证轮换、成本控制和灾难程序。" }, { "name": "访问与供应商分离", "requirement": "盘点账号、密钥、域名、云资源、订阅、第三方和数据副本；完成转移或撤销，并按需保留签署删除证据。" }, { "name": "知识与连续性", "requirement": "按照角色培训并进行见证演练；定义质保、过渡支持、服务水平、升级、替换方案和未解决责任。" } ] } ], "procedure": [ { "position": 1, "name": "尽早约定退出安排", "instruction": "交付开始前，在合同中写明资产、格式、所有权、验证、访问转移、删除、支持、费用和验收。" }, { "position": 2, "name": "持续建立资产登记", "instruction": "记录每个系统、代码库、数据资产、凭证负责人、依赖、许可、文档、证据集和接收人。" }, { "position": 3, "name": "进行接收团队演练", "instruction": "要求新负责人部署、监控、调查一次失败、回退、轮换访问并完成一项受控变更。" }, { "position": 4, "name": "签署最终处置", "instruction": "记录已经接受的资产、缺口、剩余风险、供应商保留数据、已经撤销的访问、支持结束日期和签署人。" } ], "frequentlyAskedQuestions": [ { "question": "提示词应该由谁拥有？", "answer": "所有权和可重用范围应该清楚；更重要的是企业取得运营流程所需的提示词、版本、评估证据、依赖和变更程序。" }, { "question": "只有源代码是否足够？", "answer": "不够。缺少数据契约、配置、基础设施、评估、权限、运营手册、凭证、决策和已经培训的负责人时，源代码未必能够重现服务。" }, { "question": "什么时候应该开始退出规划？", "answer": "在采购和签约时。退出要求会持续影响架构、证据、所有权、数据处理和商务条款。" }, { "question": "如果系统由供应商托管怎么办？", "answer": "按照业务重要程度要求导出格式、获取时限、连续性安排、删除证据、过渡支持和经过测试的替换路径。" } ] } }, "limitations": [ "This asset is provider-authored and is not independent validation or a claim of client results.", "It is an implementation aid, not legal, privacy, security, financial, procurement, or regulatory advice.", "Thresholds and controls must be adapted to the organisation, workflow, jurisdiction, and risk owners." ] }