# IL 202 — Enterprise AI Readiness Review：行為錨點 / Behavior Anchors

> IL 202 目前沒有已核准的正式評分權重（不同於 IL 101／201／301 已有的既有評分面向與權重）。本文件
> 只針對課程頁既有的七個準備度面向，補充「狀態怎麼判斷才算合格」的行為錨點，不建立、不假設任何新的
> 權重或計分公式；正式權重需由課程負責人另行核准。/ IL 202 does not yet have an approved formal
> scoring-weight set (unlike IL 101/201/301, which already have one). This document only adds behavior
> anchors for how to judge each of the seven existing readiness domains' status; it does not invent or
> assume any new weight or scoring formula. Formal weights require separate approval from the course
> owner.
>
> 四種狀態 / Four statuses: ready、conditional、not_ready、not_applicable（見課程模組 4）。

## 中文

| 面向 | 不合格（判為 not_ready 或誤標 not_applicable） | 合格（ready 或有效的 conditional） |
|---|---|---|
| 資料準備度 | 資料清單不完整，或既有授權範圍是否涵蓋 AI 用途完全未確認 | 逐項資料都標記分類與授權範圍，缺口已列為條件並有負責人 |
| 安全準備度 | 最小權限矩陣以個人姓名而非角色設計，或撤權演練從未實際執行 | 矩陣以角色設計，撤權流程已實際演練並記錄耗時與缺口 |
| 隱私準備度 | 把「案件主題不是個資」誤判為「不含個資」而標記 not_applicable | 明確檢查資料本身是否含個人資料，而非只看案件表面主題 |
| 整合準備度 | 直接開放寫入權限，未先以唯讀連接驗證資料格式與延遲 | 已完成唯讀整合測試，寫入權限（若有）範圍明確且有獨立稽核 |
| 治理準備度 | 沒有明確的決策權責，或核准紀錄無法追溯到具體版本 | Charter 與決策權責已核准，且與本專案目前範圍一致 |
| 營運準備度 | Runbook 只在團隊內部驗證過，沒有真正演練過任何異常情境 | 已演練至少三種異常情境，runbook 經未參與者測試可執行 |
| 人員準備度 | 只有訓練紀錄，沒有確認使用者是否理解何時該轉人工 | 使用者已理解人工接手時機，且參與過至少一次異常演練 |

## English

| Domain | Not adequate (not_ready, or a mistaken not_applicable) | Adequate (ready, or an effective conditional) |
|---|---|---|
| Data readiness | The data list is incomplete, or whether existing authorization covers AI use is completely unconfirmed | Every item is tagged with a classification and authorization scope; gaps are logged as conditions with an owner |
| Security readiness | The least-privilege matrix is designed around individual names rather than roles, or the revocation drill was never actually run | The matrix is role-based; the revocation process has actually been drilled, with timing and gaps recorded |
| Privacy readiness | Mistaking "the case topic is not personal data" for "it contains no personal data" and marking it not_applicable | The data itself, not just the surface topic of the case, is explicitly checked for personal data |
| Integration readiness | Write access is opened directly without first validating format and latency through a read-only connection | Read-only integration testing is complete; any write access is narrowly scoped with its own audit trail |
| Governance readiness | No clear decision rights, or the approval record cannot be traced to a specific version | The charter and decision rights are approved and consistent with the project's current scope |
| Operations readiness | The runbook has only been validated inside the team, never actually drilled against any incident | At least three incident scenarios have been drilled; the runbook has been tested and followed by someone uninvolved |
| People readiness | Only training records exist, with no confirmation that users understand when to hand off to a human | Users understand when to hand off to a human, and have taken part in at least one incident drill |