88 KiB
88 KiB
資安供應鏈整體進度
| 項目 | 內容 |
|---|---|
| 日期 | 2026-05-17 |
| 狀態 | S0/S1 read-only evidence 建置中 |
| 本階段完成 | 資安供應鏈 contract manifest + Source Control Approval Board + Draft Reconcile Plan + Ref Detail Diff + Ref Truth Classification + Source Control Ref Truth Owner Response 收件包 + GitHub Primary Readiness Gate + GitHub Primary Rollback ADR + GitHub Target Owner Decision Response 收件包 + Gitea 認證清冊匯出請求 + Gitea 認證清冊匯入驗收契約 + Gitea 清冊覆蓋 Owner Attestation + Gitea Owner Attestation Approval Lane 對齊 + Gitea Owner Attestation Response 收件包 + Workflow / Secret Name Inventory + Workflow / Secret Name Local Evidence + Workflow / Secret Name Redacted Export Request + Workflow / Secret Name Owner Response 收件包 + Source Control Owner Response Validation Rollup + Kali 112 live integration status + Security Finding contract + Kali scan scope approval package + Security Approval Queue + S3 人工批准 Gate + S3 人工決策紀錄 + S3 人工審查封包 + S3 人工決策狀態轉移 + S3 後續 runtime gate 準備契約 + 鏡像 readiness index + 鏡像接收計畫 + 鏡像事件信封 + 鏡像路由矩陣 + 鏡像驗收契約 + 鏡像隔離契約 + 鏡像 dry-run 報告契約 + 鏡像狀態彙整契約 + IwoooS 前端態勢入口 + IwoooS posture projection contract + IwoooS 既有前端資安頁面整合 + IwoooS 覆蓋與邊界矩陣 + IwoooS 只讀資安處理旅程 + IwoooS owner evidence readiness board + IwoooS host coverage view + IwoooS host action gate matrix + IwoooS host evidence readiness board + IwoooS host evidence collection order + IwoooS host evidence intake preflight + IwoooS host evidence review outcome lanes + IwoooS host evidence review handoff packets + IwoooS host evidence reviewer checklist + IwoooS host evidence reviewer outcome lanes + IwoooS host owner decision candidate packets + IwoooS host owner decision review checklist + IwoooS host owner decision review outcome lanes + IwoooS host owner decision record draft packets + IwoooS host owner decision record draft review checklist + IwoooS host owner decision record draft review outcome lanes + IwoooS host owner decision record write-up packets + IwoooS host owner decision record write-up review checklist + IwoooS host owner decision record write-up review outcome lanes + IwoooS host owner decision record formal candidate packets + IwoooS host owner decision record formal candidate review checklist + IwoooS host owner decision record formal candidate review outcome lanes + IwoooS host owner decision record formal record queue packets + IwoooS host owner decision record formal record queue review checklist + IwoooS host owner decision record formal record queue review outcome lanes + IwoooS host owner decision record human handoff readiness packets + IwoooS host owner decision record human handoff readiness review checklist + IwoooS host owner decision record human handoff readiness review outcome lanes + IwoooS host owner decision record human record owner review candidate packets + IwoooS host owner decision record human record owner review candidate checklist + IwoooS host owner decision record human record owner review candidate outcome lanes + IwoooS host owner decision record human record owner review preparation packets + IwoooS host owner decision record human record owner review preparation checklist + IwoooS progress acceleration lanes + IwoooS owner response next-action focus + IwoooS S4.9 owner response preflight + IwoooS S4.9 owner response request templates + IwoooS progress hold movement gates + IwoooS AwoooP read-only landing readiness + IwoooS AwoooP cross-session handoff packets + AwoooP 首頁 IwoooS 資安鏡像候選 + AwoooP 工作鏈路 IwoooS 資安鏡像候選 + AwoooP 審批佇列 IwoooS owner response 只讀焦點 |
| 本階段追加 | AwoooP 合約儀表板 IwoooS 資安契約只讀候選 + AwoooP 租戶管理 IwoooS 資安租戶範圍只讀候選 + AwoooP Run 監控 IwoooS Run State 只讀候選 + 既有安全 / 合規頁面 IwoooS 只讀反向橋接 |
| 原則 | 低摩擦分階段；文件、schema、read-only evidence 優先；不做 runtime enforcement、不切 primary |
0. 本階段完成後整體進度
0.1 2026-05-17 整體進度估算
| 進度面向 | 估算 | 判讀 |
|---|---|---|
| 整體資安網 | 58% | 框架與只讀治理已成形，仍等待 owner response、redacted payload、runtime gate 與 GitHub primary readiness |
| 框架 / 治理 / 文件 / schema / read-only evidence | 80-85% | 36 個主要 contract 中 33 ready、2 partial、1 contract-only、0 blocked |
| 真正落地執行 / runtime ingestion / GitHub primary / AwoooP production landing | 35-40% | owner response 仍 0、active runtime gate 仍 0、payload ingestion=false、github_primary_ready_count=0 |
這個進度估算用於雙 Session 同步與階段判讀，不是 approval、runtime execution、GitHub primary cutover 或 Kali scan authorization。現階段仍維持統帥要求的低摩擦策略：先建完整框架與 evidence，之後再分階段收斂。
本估算可用以下只讀 guard 驗證：
python3 scripts/security/security-mirror-progress-guard.py
0.2 Headline 58% 不代表停滯
近期 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks、S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks、S4.12 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks、S4.13 evidence routing rules / display sections / state transition rules / reviewer checklist / reviewer outcome lanes / reviewer audit event templates / reviewer audit display sections / reviewer audit collection checks / reviewer audit redaction examples / reviewer audit retention rules / reviewer audit retention checks / reviewer audit handoff packets / reviewer audit handoff checks / parallel session sync checks / parallel session conflict lanes / parallel session recovery checks / recovery outcome lanes、S1.3 non-blocking escalation lanes、S2.8 IwoooS frontend posture entry，以及 S2.9-S2.59 IwoooS / AwoooP security projection contract 都是有效進展，但它們是 framework detail，不是 owner response、runtime gate、production ingestion 或 GitHub primary readiness。因此 headline 仍維持 58%，避免把只讀框架誤算成已落地執行。
S2.50 也把「為什麼 58% 還不動」拆成五個可見 gate：owner response accepted、redacted payload ingestion、active runtime gate、GitHub primary ready、AwoooP read-only landing。這五個 gate 目前仍全部是 0 / false，所以 headline 不應被灌水提高。
| 最近完成 | 目前狀態 | headline delta |
|---|---|---|
| S4.10 request packet | 已完成草案，只顯示 owner 要回覆什麼 | 0 |
| S4.10 template status ledger | 已完成草案，7 個 targets 仍 waiting owner response | 0 |
| S4.10 audit event templates | 已完成草案，emitted_event_count=0 |
0 |
| S4.10 redaction examples | 已完成草案，只示範脫敏 metadata shape | 0 |
| S4.10 collection checks | 已完成草案，只維持 request / received / accepted 狀態分離 | 0 |
| S4.10 intake preflight checks | 已完成草案，只分類可收、補證、隔離或拒收 | 0 |
| S4.11 request packet | 已完成草案，只顯示 owner 要回覆哪 5 類 refs truth 問題 | 0 |
| S4.11 template status ledger | 已完成草案，5 類 refs truth responses 仍 waiting owner response | 0 |
| S4.11 audit event templates | 已完成草案，emitted_event_count=0 |
0 |
| S4.11 redaction examples | 已完成草案，只示範脫敏 metadata shape | 0 |
| S4.11 collection checks | 已完成草案，只維持 request / received / accepted 狀態分離 | 0 |
| S4.11 intake preflight checks | 已完成草案，只分類可審、補證、隔離、拒收或等待 | 0 |
| S4.12 request packet | 已完成草案，只顯示 owner 要回覆哪 5 類 workflow / secret 名稱問題 | 0 |
| S4.12 template status ledger | 已完成草案，5 類 workflow / secret 名稱 responses 仍 waiting owner response | 0 |
| S4.12 audit event templates | 已完成草案，emitted_event_count=0，只定義脫敏 metadata |
0 |
| S4.12 redaction examples | 已完成草案，只示範安全 metadata shape | 0 |
| S4.12 collection checks | 已完成草案，只維持 request / received / accepted 狀態分離 | 0 |
| S4.12 intake preflight checks | 已完成草案，只分類可審、補證、隔離或拒收 | 0 |
| S4.13 evidence routing rules | 已完成草案，只路由 owner evidence pointer 到補證、隔離、拒收、跨包 review 或只讀更新 | 0 |
| S4.13 display sections | 已完成草案，只固定 AwoooP Operator Console 的 read-only 呈現順序 | 0 |
| S4.13 state transition rules | 已完成草案，只固定 owner response validation 的 read-only 狀態語義 | 0 |
| S4.13 reviewer checklist | 已完成草案，只提供人工審查順序與只讀檢查提示 | 0 |
| S4.13 reviewer outcome lanes | 已完成草案，只分類等待、補證、隔離、拒收、跨包 review、只讀候選或等待 runtime gate | 0 |
| S4.13 reviewer audit event templates | 已完成草案，只定義未來可留痕的脫敏 metadata，emitted 仍為 0 | 0 |
| S4.13 reviewer audit display sections | 已完成草案，只固定 audit templates、允許 metadata、禁止 payload、0 emitted 與非授權邊界的顯示方式 | 0 |
| S4.13 reviewer audit collection checks | 已完成草案，只檢查 metadata-only、forbidden payload blocked、emitted=0、無 runtime side effect 與 counters 不變 | 0 |
| S4.13 reviewer audit redaction examples | 已完成草案，只示範 reviewer audit metadata 的安全顯示形狀 | 0 |
| S4.13 reviewer audit retention rules | 已完成草案，只定義 reviewer audit metadata 可保留的安全形狀與 raw payload 拒收邊界 | 0 |
| S4.13 reviewer audit retention checks | 已完成草案，只確認 retention rules 可見、metadata-only、raw payload / secret retention blocked、counter snapshot-only 與無 runtime side effect | 0 |
| S4.13 reviewer audit handoff packets | 已完成草案，只整理跨 Session resume、必讀 source packets、安全顯示欄位、禁止 runtime 誤讀、下一個 owner response focus 與後續 gates | 0 |
| S4.13 reviewer audit handoff checks | 已完成草案，只確認 handoff packets 可見、counters 不變、source packets 必讀、安全顯示欄位、runtime 誤讀阻擋與 next focus 未被標記 received | 0 |
| S4.13 parallel session sync checks | 已完成草案，只確認同一 PR 分支、latest delta、0 counters、false flags、source-control mutation 禁令與 S4.9 next focus | 0 |
| S4.13 parallel session conflict lanes | 已完成草案，只把 stale branch、stale delta、counter drift、runtime flag drift、source-control mutation request 與 next focus drift 分流到停下重讀或人工 review | 0 |
| S4.13 parallel session recovery checks | 已完成草案，只確認 conflict lane 後要重抓遠端、重讀 latest ledger、重跑只讀 guards、review diff、確認 false flags 與回到 S4.9 next focus | 0 |
| S4.13 parallel session recovery outcome lanes | 已完成草案，只分類 ready、branch diverged、ledger stale、guard failed、diff out-of-scope、runtime flag drift 或 next focus drift | 0 |
| S1.3 low-friction non-blocking escalation lanes | 已完成草案，只確認 LOW / MEDIUM、缺 owner response、partial mirror、source-control drift、Kali observe finding、workflow / secret name gap 與 headline holding 維持 observe / warn | 0 |
| S2.8 IwoooS frontend posture entry | 已完成草案，新增 /iwooos read-only Security Posture / Exposure 入口，顯示 58%、35 contracts、Kali / source-control / approval boundary 與 non-blocking lanes |
0 |
| S2.9 IwoooS posture projection contract | 已完成草案，新增 iwooos_posture_projection_v1，把 /iwooos 的 posture、progress、lanes、evidence refs 與 forbidden actions 固定成可驗證 snapshot |
0 |
| S2.10 IwoooS existing frontend surface integration | 已完成草案，將前端既有 /security-compliance、/security、/compliance、/alerts、/errors、/authorizations、/governance、/alert-operation-logs、/awooop/approvals、/code-review 收成 IwoooS 只讀索引 |
0 |
| S2.11 IwoooS surface coverage boundary matrix | 已完成草案，將 10 個既有前端資安頁面分成訊號與暴露面、人工控制、治理與稽核、工程審查四面，並補 5 個重疊 / 衝突控制 | 0 |
| S2.12 IwoooS operator journey projection | 已完成草案，將讀態勢、開既有頁面、判讀非阻擋分流、收 owner evidence、等待人工決策、準備後續 runtime gate 固定為 6 個只讀旅程階段 | 0 |
| S2.13 IwoooS owner evidence readiness board | 已完成草案，將 S4.9 / S4.10 / S4.11 / S4.12 owner response、redacted finding ingestion、Kali scan scope、follow-up runtime gate 固定為 7 個只讀 readiness items | 0 |
| S2.14 IwoooS host coverage view | 已完成草案，將 Kali 112、開發主機 168、開發主機 111 固定為 3 個只讀 host coverage items；active scan、SSH 變更、主機更新、credentialed scan 與 runtime control 仍未批准 | 0 |
| S2.15 IwoooS host action gate matrix | 已完成草案，將 active scan、credentialed scan、Kali /execute、SSH / host change、Kali update、runtime blocking control 固定為 6 個只讀 gate items |
0 |
| S2.16 IwoooS host evidence readiness board | 已完成草案，將 scope boundary、owner decision、credential handling、maintenance window、rollback plan、validation metrics、redacted ingestion 固定為 7 個只讀 readiness items | 0 |
| S2.17 IwoooS host evidence collection order | 已完成草案，將七個主機 evidence readiness items 排成只讀收件順序與依賴關係；received / accepted 仍為 0 | 0 |
| S2.18 IwoooS host evidence intake preflight | 已完成草案，將主機 evidence 進人工 review 前的 metadata pointer、dependency、scope、owner decision、credential plaintext、raw payload 與 counter freeze 預檢顯示成只讀規則 | 0 |
| S2.19 IwoooS host evidence review outcome lanes | 已完成草案，將 preflight 後的 ready for human review、needs scope、needs owner decision、quarantine、reject raw payload、reject credential plaintext 與 waiting runtime gate 顯示成只讀分流 | 0 |
| S2.20 IwoooS host evidence review handoff packets | 已完成草案，將 scope summary、owner decision、credential handling、maintenance / rollback、validation metrics、redaction attestation 與 runtime gate pointer 顯示成七個只讀交接包 | 0 |
| S2.21 IwoooS host evidence reviewer checklist | 已完成草案，將 scope boundary、owner decision、credential handling、redaction、maintenance / rollback、validation metrics 與 runtime gate separation 顯示成七個只讀 reviewer checks | 0 |
| S2.22 IwoooS host evidence reviewer outcome lanes | 已完成草案，將 owner decision candidate、scope mismatch、owner expired、credential metadata failed、redaction failed、rollback missing 與 runtime gate required 顯示成七個只讀 outcome lanes | 0 |
| S2.23 IwoooS host owner decision candidate packets | 已完成草案，將 scope approval、scan mode、credential handling、maintenance window、rollback owner、validation metrics 與 runtime gate 顯示成七個只讀 owner decision candidate packets | 0 |
| S2.24 IwoooS host owner decision review checklist | 已完成草案，將 scope readable、scan mode not authorization、credential metadata-only、maintenance not change、rollback owner、validation metrics 與 runtime gate separation 顯示成七個只讀 owner review checks | 0 |
| S2.25 IwoooS host owner decision review outcome lanes | 已完成草案，將 ready for decision record、scope refresh、scan mode scope review、credential boundary failed、maintenance window missing、rollback owner missing 與 runtime gate required 顯示成七個只讀 owner review outcome lanes | 0 |
| S2.26 IwoooS host owner decision record draft packets | 已完成草案，將 scope statement、scan mode、credential boundary、maintenance constraints、rollback owner、validation metrics 與 runtime gate pointer 顯示成七個只讀 decision record 草稿包 | 0 |
| S2.27 IwoooS host owner decision record draft review checklist | 已完成草案，將 scope statement complete、scan mode still not approval、credential boundary metadata only、maintenance constraints readable、rollback owner readable、validation metrics linked 與 runtime gate still closed 顯示成七個只讀草稿核對項 | 0 |
| S2.28 IwoooS host owner decision record draft review outcome lanes | 已完成草案，將 ready for write-up、scope draft incomplete、scan mode ambiguous、credential boundary incomplete、maintenance constraints incomplete、rollback owner incomplete 與 runtime gate still required 顯示成七個只讀草稿核對結果分流 | 0 |
| S2.29 IwoooS host owner decision record write-up packets | 已完成草案，將 decision summary、approved scope、scan mode limits、credential boundary、maintenance / rollback、validation evidence 與 runtime gate pointer 顯示成七個只讀正式撰寫欄位 | 0 |
| S2.30 IwoooS host owner decision record write-up review checklist | 已完成草案，將 decision summary readable、scope / expiry complete、scan mode limits explicit、credential metadata-only、maintenance / rollback linked、validation evidence linked 與 runtime gate separate 顯示成七個只讀核對項 | 0 |
| S2.31 IwoooS host owner decision record write-up review outcome lanes | 已完成草案，將 ready for formal record candidate、decision summary needs clarification、scope / expiry needs refresh、scan mode limits ambiguous、credential boundary failed、maintenance / rollback incomplete 與 runtime gate still required 顯示成七個只讀結果分流 | 0 |
| S2.32 IwoooS host owner decision record formal candidate packets | 已完成草案，將 record identity、decision summary、approved scope、scan mode limits、credential boundary、maintenance / rollback、validation / runtime gate 顯示成七個只讀 formal candidate 欄位 | 0 |
| S2.33 IwoooS host owner decision record formal candidate review checklist | 已完成草案，將 record identity traceable、decision summary readable、scope / expiry consistent、scan limits not authorization、credential metadata-only、maintenance / rollback traceable 與 runtime gate closed 顯示成七個只讀候選核對項 | 0 |
| S2.34 IwoooS host owner decision record formal candidate review outcome lanes | 已完成草案，將 ready for human record queue、identity needs trace、summary needs clarification、scope / expiry refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete 與 runtime gate required 顯示成八個只讀結果分流 | 0 |
| S2.35 IwoooS host owner decision record formal record queue packets | 已完成草案，將 queue identity、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、validation / runtime gate、no-execution attestation 顯示成八個只讀佇列資料包 | 0 |
| S2.36 IwoooS host owner decision record formal record queue review checklist | 已完成草案，將 queue identity traceable、decision summary readable、scope / expiry fresh、scan limits not authorization、credential metadata-only、maintenance / rollback linked、validation gate separate、no-execution attestation present 顯示成八個只讀核對項 | 0 |
| S2.37 IwoooS host owner decision record formal record queue review outcome lanes | 已完成草案，將 ready for human record owner handoff、identity trace refresh、summary clarification、scope / expiry refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate required 顯示成八個只讀結果分流 | 0 |
| S2.38 IwoooS host owner decision record human handoff readiness packets | 已完成草案，將 handoff identity、owner boundary、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、runtime gate separation 顯示成八個只讀 readiness packets | 0 |
| S2.39 IwoooS host owner decision record human handoff readiness review checklist | 已完成草案，將 identity trace、owner boundary、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、runtime gate separation 顯示成八個只讀 checklist items | 0 |
| S2.40 IwoooS host owner decision record human handoff readiness review outcome lanes | 已完成草案，將 ready candidate、identity trace refresh、owner boundary clarification、decision summary clarification、scope / expiry refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate required 顯示成九個只讀 outcome lanes | 0 |
| S2.41 IwoooS host owner decision record human record owner review candidate packets | 已完成草案，將 candidate identity、owner boundary、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、validation / runtime gate、no-execution attestation 顯示成九個只讀 candidate packets | 0 |
| S2.42 IwoooS host owner decision record human record owner review candidate checklist | 已完成草案，將 identity traceable、owner boundary readable、decision summary readable、scope / expiry current、scan limits not authorization、credential metadata-only、maintenance / rollback traceable、validation / runtime gate separate、no-execution attestation present 顯示成九個只讀 checklist items | 0 |
| S2.43 IwoooS host owner decision record human record owner review candidate outcome lanes | 已完成草案，將 ready for human record owner review preparation candidate、identity trace refresh、owner boundary clarification、decision summary clarification、scope / expiry refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate required 顯示成九個只讀結果分流 | 0 |
| S2.44 IwoooS host owner decision record human record owner review preparation packets | 已完成草案，將 preparation identity trace、owner boundary、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、validation / runtime gate、no-execution attestation 顯示成九個只讀 preparation packets | 0 |
| S2.45 IwoooS host owner decision record human record owner review preparation checklist | 已完成草案，將 preparation identity trace readable、owner boundary readable、decision summary readable、scope / expiry current、scan limits not authorization、credential metadata-only、maintenance / rollback traceable、validation / runtime gate separate、no-execution attestation present 顯示成九個只讀核對項 | 0 |
| S2.46 IwoooS progress acceleration lanes | 已完成草案，將 owner response、redacted ingestion、runtime gate、GitHub readiness、AwoooP landing 與 cadence compression 六個真正會影響進度感的解鎖 lane 顯示在 IwoooS；headline 仍只在高層 gate 有 evidence 時 review | 0 |
| S2.47 IwoooS owner response next-action focus | 已完成草案，將 S4.9 Gitea owner attestation 固定為下一個收件焦點，S4.10 / S4.11 / S4.12 依序排隊；received / accepted 仍為 0 | 0 |
| S2.48 IwoooS S4.9 owner response preflight | 已完成草案，將 S4.9 六個收件前檢查顯示在 IwoooS；request sent、received / accepted / rejected、preflight passed、audit emitted 仍為 0 | 0 |
| S2.49 IwoooS S4.9 owner response request templates | 已完成草案，將 S4.9 五個 request-ready-not-sent templates 顯示在 IwoooS；request sent、received / accepted / rejected、audit emitted 仍為 0 | 0 |
| S2.50 IwoooS progress hold movement gates | 已完成草案，將 58% 維持原因拆成 owner response accepted、redacted payload ingestion、active runtime gate、GitHub primary ready、AwoooP read-only landing 五個 gate；全部仍為 0 / false | 0 |
| S2.51 IwoooS AwoooP read-only landing readiness | 已完成草案，將 AwoooP 只讀接入前的 rollup snapshot、evidence refs、guard checks、route groups、forbidden outputs 與 production handoff pending 顯示在 IwoooS；production_landing_enabled 仍為 false | 0 |
| S2.52 IwoooS AwoooP cross-session handoff packets | 已完成草案，將另一個 Session 接手前的 PR / branch、progress semantics、guard commands、forbidden runtime actions、read-only inputs 與 next coordination gate 顯示在 IwoooS；production_landing_enabled 仍為 false | 0 |
| S2.53 AwoooP home IwoooS security mirror candidate | 已完成草案，將 IwoooS / security mirror headline、framework、runtime、active gates 與四個接入檢查放入 AwoooP 首頁只讀候選面板；production_landing_enabled 仍為 false | 0 |
| S2.54 AwoooP work-items IwoooS security mirror candidate | 已完成草案，將 IwoooS / security mirror 顯示成 AwoooP 工作鏈路的觀察期只讀工作項；production_landing_enabled 仍為 false，active runtime gates 仍為 0 | 0 |
| S2.55 AwoooP approvals IwoooS owner response gate candidate | 已完成草案，將 S4.9-S4.12 owner response 下一個人工收件焦點放進 AwoooP 審批佇列的只讀面板；approval_record_created=false、runtime gate 仍為 0 | 0 |
| S2.56 AwoooP contracts IwoooS security contract candidate | 已完成草案，將四個 security mirror contract refs 放進 AwoooP 合約儀表板只讀面板；contract_publish_authorized=false、runtime gate 仍為 0 | 0 |
| S2.57 AwoooP tenants IwoooS tenant scope candidate | 已完成草案，將 AWOOOI first tenant、IwoooS security mirror、host coverage=3 與 owner response waiting 放進 AwoooP 租戶管理只讀面板；tenant_migration_mode_changed=false、tenant policy changes 仍為 0 | 0 |
| S2.58 AwoooP runs IwoooS run state candidate | 已完成草案，將 security mirror Run State、read-only dry-run-only、owner response waiting 與 active runtime gates 0 放進 AwoooP Run 監控只讀面板；security_run_created=false、execution_router_linked=false | 0 |
| S2.59 existing security pages IwoooS reverse bridge | 已完成草案，將 SecurityPanel、CompliancePanel、standalone /security 與 /compliance 反向顯示 IwoooS 只讀納管狀態；runtime_execution_authorized=false、active_runtime_gate_count=0、action_buttons_allowed=false |
0 |
headline 要再往上，需要 S4.9 / S4.10 / S4.11 / S4.12 任一 owner response 收到並通過脫敏驗收，或人工批准後出現 active runtime gate、redacted payload ingestion、GitHub primary readiness 這類落地 evidence。
| 階段 | 狀態 | 目前結果 | 下一個 gate |
|---|---|---|---|
| S0 文件與契約同步 | 完成 | Kali / Codex / GitHub / Gitea / AwoooP 邊界已文件化，核心 schema 草案已建立 | AwoooP 只讀 mirror 消費 |
| S1 source-control read-only inventory | 進行中 | 已有 Gitea/GitHub refs、Gitea public-only user repo list、本機 remote、GitHub target probe、canonical lineage、110 refs evidence | Gitea private/internal 全量 repo list |
| S1.0 Gitea 全量 inventory approval | 完成草案 | 已建立 read-only token / admin export approval package | 統帥或 repo owner 批准 |
| S1.1 GitHub target 決策 | 完成草案 | 8 個 target 候選，7 個需人工批准；3 個 not_found_or_private 不得自動建立；S4.10 已補 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包 |
owner / visibility / canonical response |
| S1.2 GitHub target 逐 repo approval | 完成草案 | 7 個 approval-required targets 已拆成逐 repo pending package，並彙整成 8-item approval board；S4.10 目前 response 0 筆 | 低摩擦逐項批准 |
| S1.2a refs reconcile plan | 完成草案 | awoooi、clawbot-v5、wooo-aiops 已產生 draft plan；狀態仍為 draft_blocked |
authenticated inventory + branch/tag diff + single-repo approval |
| S1.2b branch/tag detail diff | 完成草案 | 3 個 refs-blocked mapped repos 已完成 branch/tag 明細 diff；已忽略本 PR 分支避免 evidence 自我污染 | 人工判定真相來源與 deprecated refs |
| S1.2c refs 真相來源分類 | 完成草案 | 141 個 ref review items 已分類：4 個真相來源、114 個 drift deprecated 候選、3 個 release tags、20 個 GitHub-only refs；S4.11 已補 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包 | repo owner 單 ref / 單 repo 判定 |
| S1.3 低摩擦 rollout policy | 完成草案 | observe-first / mirror-only matrix 已建立，並補 7 條 non-blocking escalation lanes：LOW / MEDIUM、缺 owner response、partial mirror、source-control drift、Kali observe finding、workflow / secret name gap、headline holding；全部 runtime_blocking_allowed=false |
AwoooP read-only policy 消費，不把 follow-up 直接升 blocking |
| S1.4 契約索引 | 完成草案 | 36 個主要 contract 已集中成 manifest；最新新增 IwoooS posture projection contract | AwoooP / IwoooS mirror-only contract registry |
| S1.5 Kali 112 live 整合狀態 | 完成第一波 | 112 已登入盤點、scanner API healthy、targeted scanner packages updated、Asia/Taipei timezone、no reboot required | scan result ingestion + /execute high-risk gate |
| S1.6 Kali finding / scan scope approval | 完成草案 | security_finding_v1 sample snapshot 與 kali_scan_scope_approval_v1 approval package 已建立；111/168 已納入 observe-only scope |
人工批准 safe crawl / credentialed scan / runtime ingestion / full-upgrade gate |
| S1.7 Security approval queue | 完成草案 | 8 個 approval queue items 已集中：7 pending approval、1 block candidate；AwoooP 可 mirror 但不得執行 | 先 review redacted finding ingestion，再 review safe crawl / Gitea inventory |
| S2 AwoooP mirror-only readiness | 完成草案 | security_mirror_readiness_v1 已整理 36 個 contracts：33 ready、2 partial、1 contract-only、0 blocked |
AwoooP 主線建立只讀入口 |
| S2.1 AwoooP mirror-only intake plan | 完成草案 | security_mirror_intake_plan_v1 已建立 5 個 intake waves 與 4 個 acceptance gates |
AwoooP 主線照 wave mirror，不新增 execution router |
| S2.2 AwoooP 鏡像事件信封 | 完成草案 | security_mirror_event_v1 已建立，要求每筆鏡像 payload 標示 execution_authorized=false 與 action_buttons_allowed=false |
AwoooP 鏡像 payload 統一信封 |
| S2.3 AwoooP 鏡像路由矩陣 | 完成草案 | security_mirror_route_v1 已建立 5 個 route groups，定義目的地、channel policy 與 review lane |
AwoooP 消費時不猜路由、不新增執行入口 |
| S2.4 AwoooP 鏡像驗收契約 | 完成草案 | security_mirror_acceptance_v1 已建立 8 個 acceptance checks；blocking 只針對鏡像資料不完整、未脫敏或進度估算被誤當授權 |
AwoooP 接入時可驗收，不升級成 runtime enforcement |
| S2.5 AwoooP 鏡像隔離契約 | 完成草案 | security_mirror_quarantine_v1 已建立 5 個 quarantine lanes；失敗 payload 必須等新 snapshot commit 後才能 retry |
AwoooP 可隔離壞資料，不阻擋 runtime |
| S2.6 AwoooP 鏡像 dry-run 報告契約 | 完成草案 | security_mirror_dry_run_v1 已建立 8 個 dry-run steps，已納入 CHECK_PROGRESS_GUARD 與 CHECK_OWNER_RESPONSE_GUARD；latest local validation 為 repo_snapshot_guard_pass；目前狀態仍為 contract defined not executed |
AwoooP 未來可回報演練結果，但不啟動 production ingestion |
| S2.7 AwoooP 鏡像狀態彙整契約 | 完成草案 | security_mirror_status_rollup_v1 已建立，彙整 S0-S4、approval queue summary 與下一個安全 gate；S4.13 已補 owner response validation rollup、evidence routing rules、display sections、state transition rules、reviewer checklist、reviewer outcome lanes、reviewer audit event templates、reviewer audit display sections、reviewer audit collection checks、reviewer audit redaction examples、reviewer audit retention rules、reviewer audit retention checks、reviewer audit handoff packets、reviewer audit handoff checks、parallel session sync checks、parallel session conflict lanes、parallel session recovery checks 與 parallel session recovery outcome lanes |
兩個 Session 用同一份 rollup 同步，不誤啟執行面 |
| S2.8 IwoooS 前端態勢入口 | 完成草案 | 已新增 /iwooos、Sidebar 入口與 Command Palette 入口；以 Security Posture / Exposure Management 方式顯示目前資安網狀態、Kali 112、source-control supply chain、approval boundary、non-blocking lanes 與 evidence refs |
使用者可看懂資安網進度與邊界，但不新增執行按鈕 |
| S2.9 IwoooS 前端投影契約 | 完成草案 | iwooos_posture_projection_v1 已建立，manifest / readiness / route / acceptance / dry-run / event sample 已同步 36 contracts / 33 ready 口徑；guard 會驗證 no action button、no runtime authorization 與 7 條 non-blocking lanes |
IwoooS 顯示資料不再只是頁面常數，而是可被 AwoooP / Security Session 驗證的只讀契約 |
| S2.10 IwoooS 既有前端資安頁面整合 | 完成草案 | /iwooos 新增既有資安頁面索引，涵蓋安全合規、舊安全、舊合規、告警、錯誤與 UX 稽核、授權中心、AI 治理、告警操作日誌、AwoooP approvals、AI Code Review |
使用者能從 IwoooS 看懂原本資安能力散在哪些頁面；仍只做 link-only 顯示，不新增 scan / execute / repair / blocking gate |
| S2.11 IwoooS 覆蓋與邊界矩陣 | 完成草案 | /iwooos 新增 coverage / boundary matrix，分成 signals、human control、governance audit、engineering review 四組，並顯示 preserve owner、no runtime lift、Code Review not deploy gate、AwoooP approval not security approval、frontend index not Kali caller 五條控制 |
使用者能理解重疊頁面的責任分界；仍不新增 runtime、Kali、deploy 或 blocking control |
| S2.12 IwoooS 只讀資安處理旅程 | 完成草案 | /iwooos 新增 6 階段處理旅程：讀態勢、開既有頁面、判讀非阻擋分流、收 owner evidence、等待人工決策、準備後續 runtime gate |
使用者能理解資安工作下一步，但每一步都是 status projection，不是 execution queue 或 action button |
| S2.13 IwoooS Owner Evidence Readiness | 完成草案 | /iwooos 新增 owner evidence readiness board，顯示下一步真正影響 headline progress 的 7 個 evidence / gate 缺口 |
使用者能理解為什麼 58% 不應灌水提高；全部 received / accepted 仍為 0，不新增執行控制 |
| S2.14 IwoooS Host Coverage View | 完成草案 | /iwooos 新增主機覆蓋視圖，明確顯示 Kali 112 與 168 / 111 兩台開發主機已納入 observe-only 資安視野 |
使用者能看到指定主機已納管到資安架構視圖；仍不新增 SSH、scan、update、execute、credentialed scan 或 blocking control |
| S2.15 IwoooS Host Action Gate Matrix | 完成草案 | /iwooos 新增主機動作 gate 矩陣，將 active scan、credentialed scan、Kali /execute、SSH / host change、Kali update 與 runtime blocking control 拆成只讀 gate |
使用者能看懂主機動作為什麼仍需人工批准；仍不新增任何主機操作或 runtime enforcement |
| S2.16 IwoooS Host Evidence Readiness | 完成草案 | /iwooos 新增主機 evidence readiness board，顯示主機動作前仍缺 scope、owner decision、credential handling、maintenance window、rollback、validation metrics 與 redacted ingestion evidence |
使用者能看懂主機行動前置證據，不會把規劃誤認為已批准；仍不新增任何主機操作 |
| S2.17 IwoooS Host Evidence Collection Order | 完成草案 | /iwooos 新增主機 evidence 收件順序，將 scope、owner decision、credential handling、maintenance window、rollback、validation metrics 與 redacted ingestion 排成只讀依賴 |
使用者能知道下一步先收什麼；仍不把任何 evidence 標成 received / accepted，也不啟動掃描、SSH、更新或 runtime control |
| S2.18 IwoooS Host Evidence Intake Preflight | 完成草案 | /iwooos 新增主機 evidence intake preflight，顯示 metadata pointer、collection order、scope、owner decision、credential plaintext、raw payload 與 counter freeze 七個預檢 |
使用者能知道 evidence 送審前會先擋哪些風險；仍不收 raw payload、不收憑證明文、不推 received / accepted、不啟動 runtime |
| S2.19 IwoooS Host Evidence Review Outcome Lanes | 完成草案 | /iwooos 新增主機 evidence review outcome lanes，顯示可進人工審、補 scope、補 owner decision、隔離、拒收 raw payload、拒收憑證明文與等待 runtime gate 七個分流 |
使用者能理解 preflight 後的處理結果；仍不建立 approval record、不推 received / accepted、不啟動 runtime |
| S2.20 IwoooS Host Evidence Review Handoff Packets | 完成草案 | /iwooos 新增主機 evidence review handoff packets，顯示 scope summary、owner decision、credential handling、maintenance / rollback、validation metrics、redaction attestation、runtime gate pointer 七個交接包 |
使用者能理解送交人工 reviewer 前要準備哪些脫敏資料；仍不標記 received / accepted、不建立 approval record、不保存 raw payload / secret value、不啟動 runtime |
| S2.21 IwoooS Host Evidence Reviewer Checklist | 完成草案 | /iwooos 新增主機 evidence reviewer checklist，顯示 scope boundary match、owner decision scope / expiry、credential metadata-only、redaction pass、maintenance / rollback、validation metrics、runtime gate separated 七個檢查 |
使用者能理解人審不是執行授權；仍不標記 passed / received / accepted、不建立 approval record、不開 runtime gate |
| S2.22 IwoooS Host Evidence Reviewer Outcome Lanes | 完成草案 | /iwooos 新增主機 evidence reviewer outcome lanes，顯示 ready for owner decision、scope mismatch、owner decision expired、credential metadata failed、redaction failed、rollback missing、runtime gate required 七個分流 |
使用者能理解 checklist 後下一步；仍不標記 passed / accepted、不建立 approval record、不開 runtime gate、不執行主機動作 |
| S2.23 IwoooS Host Owner Decision Candidate Packets | 完成草案 | /iwooos 新增主機 owner decision candidate packets，顯示 scope approval、scan mode、credential handling、maintenance window、rollback owner、validation metrics、runtime gate 七個候選包 |
使用者能理解 owner 人工決策需要看哪些素材；仍不建立 decision record、不標記 approved、不開 runtime gate、不執行主機動作 |
| S2.24 IwoooS Host Owner Decision Review Checklist | 完成草案 | /iwooos 新增主機 owner decision review checklist，顯示 scope boundary readable、scan mode not authorization、credential boundary metadata only、maintenance window not change、rollback owner readable、validation metrics predefined、runtime gate still separate 七個檢查 |
使用者能理解 owner 決策前仍需核對哪些安全邊界；仍不建立 decision record、不標記 approved、不開 runtime gate、不執行主機動作 |
| S2.25 IwoooS Host Owner Decision Review Outcome Lanes | 完成草案 | /iwooos 新增主機 owner decision review outcome lanes，顯示 ready for decision record、scope needs refresh、scan mode needs scope、credential boundary failed、maintenance window missing、rollback owner missing、runtime gate required 七個分流 |
使用者能理解 owner review 後下一步；仍不標記 review passed、不建立 decision record、不標記 approved、不開 runtime gate、不執行主機動作 |
| S2.26 IwoooS Host Owner Decision Record Draft Packets | 完成草案 | /iwooos 新增主機 owner decision record draft packets，顯示 scope statement、scan mode、credential boundary、maintenance constraints、rollback owner、validation metrics、runtime gate pointer 七個草稿欄位 |
使用者能理解 formal decision record 草稿需要哪些 metadata；仍不建立 decision record、不標記 accepted、不建立 approval record、不開 runtime gate、不執行主機動作 |
| S2.27 IwoooS Host Owner Decision Record Draft Review Checklist | 完成草案 | /iwooos 新增主機 owner decision record draft review checklist，顯示 scope statement complete、scan mode still not approval、credential boundary metadata only、maintenance constraints readable、rollback owner readable、validation metrics linked、runtime gate still closed 七個核對項 |
使用者能理解 formal decision record 草稿進人審前仍需核對哪些條件；仍不標記 review passed、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.28 IwoooS Host Owner Decision Record Draft Review Outcome Lanes | 完成草案 | /iwooos 新增主機 owner decision record draft review outcome lanes，顯示 ready for decision record write-up、scope draft incomplete、scan mode ambiguous、credential boundary incomplete、maintenance constraints incomplete、rollback owner incomplete、runtime gate still required 七個分流 |
使用者能理解 draft review 後下一步；仍不標記 review passed、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.29 IwoooS Host Owner Decision Record Write-Up Packets | 完成草案 | /iwooos 新增主機 owner decision record write-up packets，顯示 decision summary、approved scope、scan mode limits、credential boundary、maintenance / rollback、validation evidence、runtime gate pointer 七個正式撰寫欄位 |
使用者能理解 ready for write-up 仍只是欄位整理；仍不標記 write-up completed、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.30 IwoooS Host Owner Decision Record Write-Up Review Checklist | 完成草案 | /iwooos 新增主機 owner decision record write-up review checklist，顯示 decision summary readable、scope / expiry complete、scan mode limits explicit、credential metadata-only、maintenance / rollback linked、validation evidence linked、runtime gate separate 七個核對項 |
使用者能理解 write-up packets 後仍需只讀核對；仍不標記 review passed、不標記 write-up completed、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.31 IwoooS Host Owner Decision Record Write-Up Review Outcome Lanes | 完成草案 | /iwooos 新增主機 owner decision record write-up review outcome lanes，顯示 ready for formal record candidate、decision summary needs clarification、scope / expiry needs refresh、scan mode limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate still required 七個分流 |
使用者能理解 write-up review 後仍只是只讀結果分流；仍不標記 review passed、不標記 write-up completed、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.32 IwoooS Host Owner Decision Record Formal Candidate Packets | 完成草案 | /iwooos 新增主機 owner decision record formal candidate packets，顯示 record identity、decision summary、approved scope、scan mode limits、credential boundary、maintenance / rollback、validation / runtime gate 七個候選欄位 |
使用者能理解 formal candidate 仍不是正式紀錄；仍不標記 finalized、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.33 IwoooS Host Owner Decision Record Formal Candidate Review Checklist | 完成草案 | /iwooos 新增主機 owner decision record formal candidate review checklist，顯示 record identity traceable、decision summary readable、scope / expiry consistent、scan limits still not authorization、credential boundary still metadata-only、maintenance / rollback traceable、runtime gate still closed 七個核對項 |
使用者能理解 formal candidate review 仍不是通過、完成或批准；仍不標記 review passed、不標記 finalized、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.34 IwoooS Host Owner Decision Record Formal Candidate Review Outcome Lanes | 完成草案 | /iwooos 新增主機 owner decision record formal candidate review outcome lanes，顯示 ready for human record queue、record identity needs trace、decision summary needs clarification、scope / expiry need refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate still required 八個分流 |
使用者能理解 formal candidate review outcome 仍不是通過、完成或批准；仍不標記 review passed、不標記 finalized、不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.35 IwoooS Host Owner Decision Record Formal Record Queue Packets | 完成草案 | /iwooos 新增主機 owner decision record formal record queue packets，顯示 queue identity、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、validation / runtime gate、no-execution attestation 八個資料包 |
使用者能理解 formal record queue packet 仍不是 enqueue 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.36 IwoooS Host Owner Decision Record Formal Record Queue Review Checklist | 完成草案 | /iwooos 新增主機 owner decision record formal record queue review checklist，顯示 identity traceable、decision summary readable、scope / expiry fresh、scan limits not authorization、credential metadata-only、maintenance / rollback linked、validation gate separate、no-execution attestation present 八個核對項 |
使用者能理解 formal record queue review 仍不是 review passed、enqueue 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.37 IwoooS Host Owner Decision Record Formal Record Queue Review Outcome Lanes | 完成草案 | /iwooos 新增主機 owner decision record formal record queue review outcome lanes，顯示 ready for human record owner handoff、identity trace refresh、decision summary clarification、scope / expiry refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate required 八個分流 |
使用者能理解 formal record queue review outcome 仍不是 review passed、enqueue 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.38 IwoooS Host Owner Decision Record Human Handoff Readiness Packets | 完成草案 | /iwooos 新增主機 owner decision record human handoff readiness packets，顯示 handoff identity、owner boundary、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、runtime gate separation 八個準備包 |
使用者能理解 handoff readiness 仍不是 handoff started、handoff ready、review passed、enqueue 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.39 IwoooS Host Owner Decision Record Human Handoff Readiness Review Checklist | 完成草案 | /iwooos 新增主機 owner decision record human handoff readiness review checklist，顯示 identity trace readable、owner boundary readable、decision summary readable、scope / expiry current、scan limits not authorization、credential metadata-only、maintenance / rollback traceable、runtime gate separate 八個核對項 |
使用者能理解 handoff readiness review 仍不是 review passed、handoff started、handoff ready、enqueue 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.40 IwoooS Host Owner Decision Record Human Handoff Readiness Review Outcome Lanes | 完成草案 | /iwooos 新增主機 owner decision record human handoff readiness review outcome lanes，顯示 ready for human record owner review candidate、identity trace needs refresh、owner boundary needs clarification、decision summary needs clarification、scope / expiry need refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate still required 九個分流 |
使用者能理解 handoff readiness review outcome 仍不是 review passed、handoff started、handoff ready、enqueue 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.41 IwoooS Host Owner Decision Record Human Record Owner Review Candidate Packets | 完成草案 | /iwooos 新增主機 owner decision record human record owner review candidate packets，顯示 candidate identity、owner boundary、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、validation / runtime gate、no-execution attestation 九個候選資料包 |
使用者能理解 human record owner review candidate packet 仍不是 review started、review ready、handoff、owner decision、正式紀錄或批准；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.42 IwoooS Host Owner Decision Record Human Record Owner Review Candidate Checklist | 完成草案 | /iwooos 新增主機 owner decision record human record owner review candidate checklist，顯示 candidate identity traceable、owner boundary readable、decision summary readable、scope / expiry current、scan limits not authorization、credential boundary metadata-only、maintenance / rollback traceable、validation / runtime gate separate、no-execution attestation present 九個核對項 |
使用者能理解 human record owner review candidate checklist 仍不是 checklist passed、review started、review ready、owner decision 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.43 IwoooS Host Owner Decision Record Human Record Owner Review Candidate Outcome Lanes | 完成草案 | /iwooos 新增主機 owner decision record human record owner review candidate outcome lanes，顯示 ready for human record owner review preparation candidate、identity trace refresh、owner boundary clarification、decision summary clarification、scope / expiry refresh、scan limits ambiguous、credential boundary failed、maintenance / rollback incomplete、runtime gate still required 九個分流 |
使用者能理解 human record owner review candidate outcome 仍不是 checklist passed、review started、review ready、owner decision 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.44 IwoooS Host Owner Decision Record Human Record Owner Review Preparation Packets | 完成草案 | /iwooos 新增主機 owner decision record human record owner review preparation packets，顯示 preparation identity trace、owner boundary、decision summary、scope / expiry、scan limits、credential boundary、maintenance / rollback、validation / runtime gate、no-execution attestation 九個準備資料包 |
使用者能理解 human record owner review preparation packet 仍不是 preparation completed、review started、review ready、owner decision 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.45 IwoooS Host Owner Decision Record Human Record Owner Review Preparation Checklist | 完成草案 | /iwooos 新增主機 owner decision record human record owner review preparation checklist，顯示 preparation identity trace readable、owner boundary readable、decision summary readable、scope / expiry current、scan limits not authorization、credential metadata-only、maintenance / rollback traceable、validation / runtime gate separate、no-execution attestation present 九個只讀核對項 |
使用者能理解 human record owner review preparation checklist 仍不是 preparation completed、checklist passed、review started、review ready、owner decision 或正式紀錄；仍不建立 decision record、不標記 accepted、不開 runtime gate、不執行主機動作 |
| S2.46 IwoooS Progress Acceleration Lanes | 完成草案 | /iwooos 新增進度加速與 58% 解鎖面板，顯示 owner response、redacted ingestion、runtime gate、GitHub readiness、AwoooP landing 與 cadence compression 六條 acceleration lanes |
使用者能理解前面看起來慢是因為 S2.38-S2.45 都是防止誤讀的 framework detail；後續改採 milestone batch，但 acceleration lane 仍不是 owner response、進度加分、runtime gate、GitHub primary 或 production execution |
| S2.47 IwoooS Owner Response Next-Action Focus | 完成草案 | /iwooos 新增 owner response 下一步收件焦點，顯示 S4.9 Gitea owner attestation 先收、S4.10 GitHub target、S4.11 refs truth、S4.12 workflow / secret name 依序排隊 |
使用者能理解下一個有感工作是收斂 P0 owner response；focus 仍不是催收、代填、received、accepted、approval record、runtime gate、repo / refs mutation、secret value collection 或 GitHub primary |
| S2.48 IwoooS S4.9 Owner Response Preflight | 完成草案 | /iwooos 新增 S4.9 owner response 收件前 preflight，顯示 known attestation item、required owner fields、allowed decision、redacted evidence only、no execution request、all five items before accepted 六個檢查 |
使用者能理解下一步不是再拆 checklist，而是把第一個 P0 owner response 的可收件條件說清楚；preflight 仍不是 request sent、received、accepted、audit emitted、Gitea write、refs sync、runtime gate 或 GitHub primary |
| S2.49 IwoooS S4.9 Owner Response Request Templates | 完成草案 | /iwooos 新增 S4.9 owner response 五個回覆 template，顯示 public-only / local gap、org/user endpoint、110 adjacent source scope、repo owner / canonical scope、legacy / inaccessible disposition |
使用者能理解第一個 owner response 要回哪五題；templates 仍不是 request sent、received、accepted、audit emitted、Gitea inventory completed、Gitea write、refs sync、token collection、runtime gate 或 GitHub primary |
| S2.50 IwoooS Progress Hold Movement Gates | 完成草案 | /iwooos 新增「為什麼 58% 還不動」五個 movement gates，顯示 owner response accepted、redacted payload ingestion、active runtime gate、GitHub primary ready、AwoooP read-only landing 仍全部未滿足 |
使用者能理解 58% 維持不是卡死，而是不灌水；gate 顯示仍不是進度加分、授權、payload ingestion、runtime gate、GitHub primary 或 production landing |
| S2.51 IwoooS AwoooP Read-Only Landing Readiness | 完成草案 | /iwooos 新增 AwoooP 只讀 landing readiness，顯示 snapshot、evidence refs、guard checks、route groups、forbidden outputs 與 production handoff pending 六個接入條件 |
使用者與另一個 AwoooP Session 能看懂主線接入要消費什麼；readiness 仍不是 production landing enabled、execution router、action button、guard skip 或 headline 加分 |
| S2.52 IwoooS AwoooP Cross-Session Handoff Packets | 完成草案 | /iwooos 新增 AwoooP 跨 Session handoff，顯示 PR / branch anchor、progress semantics、required guard commands、forbidden runtime actions、read-only inputs 與 next coordination gate 六個接手 packets |
另一個 Session 可用同一 PR / branch / guard / rollup 口徑同步；handoff 仍不是 merge、deploy、primary switch、refs mutation、guard skip、production consumption 或 headline 加分 |
| S2.53 AwoooP Home IwoooS Security Mirror Candidate | 完成草案 | /awooop 首頁新增 IwoooS 資安鏡像候選面板，顯示 58%、80-85%、35-40%、0 active runtime gates 與 projection / guard / owner response / production landing 四個檢查 |
使用者能在 AwoooP 首頁直接感受到資安網狀態；候選面板仍不是 production landing enabled、execution router、runtime gate、action button 或 headline 加分 |
| S2.54 AwoooP Work-Items IwoooS Security Mirror Candidate | 完成草案 | /awooop/work-items 新增 S2.54 IwoooS 資安鏡像只讀工作項，顯示 58%、80-85%、35-40%、active runtime gates=0、owner response waiting 與 false 邊界，並連到 /iwooos |
使用者能在工作鏈路追蹤資安網，而不是只看首頁摘要；觀察項仍不是 production landing enabled、execution router、runtime gate、action button 或 headline 加分 |
| S2.55 AwoooP Approvals IwoooS Owner Response Gate Candidate | 完成草案 | /awooop/approvals 新增 IwoooS owner response 只讀審查焦點，顯示 S4.9-S4.12 收件順序、received=0、accepted=0、active runtime gates=0、headline=58%，並連到 /iwooos |
使用者能在審批佇列理解下一個人工收件焦點；面板仍不是 approval record、runtime gate、execution router、action button 或 headline 加分 |
| S2.56 AwoooP Contracts IwoooS Security Contract Candidate | 完成草案 | /awooop/contracts 新增 IwoooS 資安契約只讀候選，顯示四個 security mirror contract refs、36 total、33 ready、2 partial、active runtime gates=0，並連到 /iwooos |
使用者能在合約儀表板理解資安網背後的契約來源；面板仍不是 contract publish、lifecycle mutation、runtime gate、execution router、action button 或 headline 加分 |
| S2.57 AwoooP Tenants IwoooS Tenant Scope Candidate | 完成草案 | /awooop/tenants 新增 IwoooS 租戶資安範圍只讀候選，顯示 AWOOOI 第一租戶、IwoooS、host coverage=3、tenant policy changes=0，並連到 /iwooos |
使用者能在租戶管理理解資安網保護範圍；面板仍不是 migration mode change、tenant policy mutation、runtime gate、execution router、action button 或 headline 加分 |
| S2.58 AwoooP Runs IwoooS Run State Candidate | 完成草案 | /awooop/runs 新增 IwoooS Run State 只讀候選，顯示 run visibility=read-only、security runs=0、active runtime gates=0、owner accepted=0，並連到 /iwooos |
使用者能在 Run 監控理解資安網仍是只讀候選；面板仍不是 platform run created、execution router linked、runtime gate、execution queue、action button 或 headline 加分 |
| S2.59 Existing Security Pages IwoooS Reverse Bridge | 完成草案 | SecurityPanel、CompliancePanel、standalone /security 與 /compliance 新增 IwoooS 只讀橋接，顯示 58%、80-85%、runtime gates=0、action buttons=0，並連到 /iwooos |
使用者回到原本安全 / 合規頁也能知道它們已納入 IwoooS；橋接仍不是 owner response、runtime authorization、scan、repair、approve、deploy 或 blocking control |
| S3 approval gate | 進行中 | security_approval_gate_v1 已建立 8 個人工 gate items：7 pending、1 block candidate、0 approved |
不得繞過人工批准；批准後仍需 follow-up runtime gate |
| S3.0 人工批准 Gate 契約 | 完成草案 | 定義批准範圍、決策選項、required reviewers、still forbidden 與 follow-up runtime gate | AwoooP 可記錄決策，不可執行 gate item |
| S3.1 人工決策紀錄契約 | 完成草案 | security_approval_decision_record_v1 已建立；目前 0 筆 decision records、0 個 runtime action 授權 |
AwoooP 可稽核決策，不可把決策當執行 |
| S3.2 人工審查封包契約 | 完成草案 | security_approval_review_packet_v1 已建立；8 個 review packets、7 ready for human review、1 block candidate、0 個 runtime action 授權 |
AwoooP 可顯示 review lane，不可把 packet 當批准或執行 |
| S3.3 人工決策狀態轉移契約 | 完成草案 | security_approval_state_transition_v1 已建立；5 個 decision options 都有 next state、0 個 runtime action 授權 |
AwoooP 可顯示決策後狀態，不可把 transition 當執行 |
| S3.4 後續 runtime gate 準備契約 | 完成草案 | security_followup_runtime_gate_v1 已建立；8 個 gate templates、0 個 active runtime gates、0 個 approved scope |
AwoooP 可顯示前置 evidence、preflight checks 與 rollback / disable requirement，不可啟用 runtime gate |
| S4.0 GitHub primary readiness gate | 完成草案 | source_control_primary_readiness_gate_v1 已建立；8 個 candidate repos、7 個 in-scope blocked、0 個 primary ready；S4.10 已補 target owner response gate；S4.11 已補 refs truth owner response gate；S4.12 已補 workflow / secret 名稱 owner response gate |
AwoooP 可顯示 parity、owner、rollback ADR 缺口，不可切 primary |
| S4.1 Workflow / Secret 名稱 inventory 契約 | 完成草案 | source_control_workflow_secret_name_inventory_v1 已建立；8 個 candidate repos、7 個 in-scope repos 尚缺實際 inventory、0 個 complete、禁止收集 secret value |
AwoooP 可顯示 workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱缺口，不可修改 workflow 或 secret |
| S4.2 Workflow / Secret 名稱 local evidence | 完成草案 | 已建立 local read-only collector 與 snapshot；7 個 local repos visible、4 個 local evidence repos、31 個 workflow files、43 個 referenced secret names、secret value detected=false | 補 webhook / deploy key / branch protection / repository secret parity 的 redacted evidence；仍不可切 primary |
| S4.3 Workflow / Secret 名稱 redacted export request | 完成草案 | 已建立 export request schema / snapshot / 人讀版；7 個 in-scope repos、5 類 export lanes：webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；write token allowed=false | repo owner 或未來只讀 API 依 request 補 redacted export；仍不可收 secret value、不可修改 GitHub/Gitea |
| S4.12 Workflow / Secret Name Owner Response 收件包 | 完成草案 | 已建立 owner response schema / snapshot / 人讀版；1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks、5 個 response templates、8 個 acceptance checks、10 個 rejection rules、candidate repos 8、in-scope repos 7、received response 0、accepted 0、audit events emitted 0、execution authorized=false | owner 依 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與模板回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；response 通過只更新 read-only inventory / export request / readiness wording，不代表收 secret value、改 workflow、啟用 runner 或 primary approval |
| S4.13 Source Control Owner Response Validation Rollup | 完成草案 | 已建立 validation rollup schema / snapshot / 人讀版；彙整 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets、4 條 missing response lanes、4 步 owner response collection order、next collection candidate、22 個 response templates、10 個 cross-packet checks、6 條 evidence routing rules、8 個 display sections、7 條 state transition rules、9 個 reviewer checklist items、7 條 reviewer outcome lanes、4 個 reviewer audit event templates、5 個 reviewer audit display sections、6 個 reviewer audit collection checks、5 個 reviewer audit redaction examples、5 條 reviewer audit retention rules、6 個 reviewer audit retention checks、6 個 reviewer audit handoff packets、6 個 reviewer audit handoff checks、6 個 parallel session sync checks、6 條 parallel session conflict lanes、6 個 parallel session recovery checks、7 條 parallel session recovery outcome lanes、40 個 rejection rules、received / accepted / rejected response 皆為 0、reviewer audit emitted 仍為 0、execution authorized=false；latest local validation 為 SOURCE_CONTROL_OWNER_RESPONSE_GUARD_OK |
AwoooP 可顯示四包 owner response 驗收總覽、缺口摘要、建議收件順序、下一個建議收件項目、evidence routing、display sections、state transition rules、reviewer checklist、reviewer outcome lanes、reviewer audit event templates、reviewer audit display sections、reviewer audit collection checks、reviewer audit redaction examples、reviewer audit retention rules、reviewer audit retention checks、reviewer audit handoff packets、handoff checks、parallel session sync checks、parallel session conflict lanes、parallel session recovery checks、parallel session recovery outcome lanes 與 quarantine rules；rollup 不代表 approval、runtime gate、production ingestion、repo / refs / workflow / secret / runner 執行授權或 primary approval |
| S4.4 GitHub Primary rollback ADR | 完成草案 | 已建立 rollback ADR schema / snapshot / 人讀版；7 個 in-scope rollback drafts、0 owner approved、0 dry-run completed、0 active cutover | repo owner 審查 rollback owner、validation window 與 triggers；仍不可切 primary 或執行 rollback |
| S4.5 Gitea 認證清冊匯出請求 | 完成草案 | 已建立匯出請求 schema / snapshot / 人讀版；目前未認證公開範圍 repo 2 個、本機可見 Gitea unique repo 4 個、覆蓋缺口 2 個、匯出來源選項 2 類；允許收集 token value=false | repo owner 依只讀 token API 或已脫敏管理匯出補私有 / 內部全量 repo list；仍不可保存 token、不可 write Gitea、不可 refs sync |
| S4.6 Gitea 認證清冊匯入驗收契約 | 完成草案 | 已建立匯入驗收 schema / snapshot / 人讀版；目前 received payload 0、accepted 0、rejected 0；定義 10 個驗收檢查、10 個拒收規則與 4 個 quarantine lanes | owner 提供脫敏 payload 後先驗收 / 拒收 / 隔離；仍不可把驗收當 primary approval |
| S4.7 Gitea 清冊覆蓋 Owner Attestation | 完成草案 | 已建立 coverage attestation schema / snapshot / 人讀版；5 個 owner decision items、received attestation 0、accepted 0、execution authorized=false | owner 判定 public-only / local remote gap、org/user endpoint、110 adjacent source、canonical owner 與 legacy/inaccessible disposition；仍不可把 attestation 當 migration approval |
| S4.8 Gitea Owner Attestation Approval Lane 對齊 | 完成草案 | 已將既有 Gitea approval queue / gate / review packet / follow-up runtime gate 對齊 S4.7 先行條件；queue items 維持 8、review packets 維持 8、active runtime gates 維持 0 | AwoooP 先顯示 5 個 attestation items，owner decision 接受前不得執行 read-only inventory 或標記 complete |
| S4.9 Gitea Owner Attestation Response 收件包 | 完成草案 | 已建立 owner response schema / snapshot / 人讀版；1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、5 個 response templates、6 個 intake preflight checks、5 個 outcome lanes、8 個 acceptance checks、10 個 rejection rules、received response 0、accepted 0、execution authorized=false | owner 依 request packet 與模板回覆 S4.7 五個 items；AwoooP 先用 template status ledger / audit event templates / redaction examples / display sections / collection checks 維持 request / received / accepted 分離，再用 preflight / outcome lanes 判斷可審、補證、隔離、拒收或等待；response 通過只更新 read-only matrix / decision table / readiness gate，不代表 inventory 執行、audit production ingestion 或 primary approval |
| S4.10 GitHub Target Owner Decision Response 收件包 | 完成草案 | 已建立 owner decision response schema / snapshot / 人讀版；1 個 owner response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks、7 個 response templates、8 個 acceptance checks、10 個 rejection rules、received response 0、accepted 0、execution authorized=false | owner 依 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與模板回覆 7 個 GitHub target 的 owner / visibility / canonical；response 通過只更新 read-only decision table / approval package / approval board / readiness gate，不代表 repo creation、visibility change、refs sync 或 primary approval |
| S4.11 Source Control Ref Truth Owner Response 收件包 | 完成草案 | 已建立 owner response schema / snapshot / 人讀版；1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks、5 個 response templates、8 個 acceptance checks、10 個 rejection rules、total ref review items 141、received response 0、accepted 0、audit events emitted 0、execution authorized=false | owner 依 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與模板回覆 main/dev truth、deprecated drift、release tag、GitHub-only refs；response 通過只更新 read-only classification / reconcile / readiness wording，不代表 refs sync、delete、force push 或 primary approval |
| S4 migration execution | 未開始 | GitHub primary 長期方向已確認，但 refs / tags / workflow / secret 名稱尚未全量驗證，rollback ADR 仍待 owner approval | SHA/tag/workflow parity、rollback ADR owner approval 與 runtime gate |
1. 已建立的主要 evidence
| 類型 | 檔案 |
|---|---|
| AwoooP handoff | docs/security/AWOOOP-SECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md |
| Mirror-only 清單 | docs/security/AWOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md |
| Gitea/GitHub migration inventory | docs/security/GITEA-GITHUB-MIGRATION-INVENTORY.md |
| Gitea server-side inventory runbook | docs/security/GITEA-SERVER-SIDE-INVENTORY-RUNBOOK.md |
| Gitea read-only inventory approval package | docs/security/GITEA-READONLY-INVENTORY-APPROVAL-PACKAGE.md |
| Gitea read-only inventory approval JSON | docs/security/gitea-readonly-inventory-approval.snapshot.json |
| Gitea 認證清冊匯出請求 | docs/security/GITEA-AUTHENTICATED-INVENTORY-EXPORT-REQUEST.md |
| Gitea 認證清冊匯出請求 JSON | docs/security/gitea-authenticated-inventory-export-request.snapshot.json |
| Gitea 認證清冊匯入驗收契約 | docs/security/GITEA-AUTHENTICATED-INVENTORY-IMPORT-ACCEPTANCE.md |
| Gitea 認證清冊匯入驗收契約 JSON | docs/security/gitea-authenticated-inventory-import-acceptance.snapshot.json |
| Gitea 清冊覆蓋 owner attestation | docs/security/GITEA-INVENTORY-COVERAGE-ATTESTATION.md |
| Gitea 清冊覆蓋 owner attestation JSON | docs/security/gitea-inventory-coverage-attestation.snapshot.json |
| Gitea owner attestation response 收件包 | docs/security/GITEA-INVENTORY-OWNER-ATTESTATION-RESPONSE.md |
| Gitea owner attestation response JSON | docs/security/gitea-inventory-owner-attestation-response.snapshot.json |
| Gitea 管理匯出 redaction checklist | docs/security/GITEA-ADMIN-EXPORT-REDACTION-CHECKLIST.md |
| Gitea org endpoint blocked evidence | docs/security/GITEA-ORG-REPO-INVENTORY-BLOCKED-SNAPSHOT.md |
| Source-control migration matrix | docs/security/SOURCE-CONTROL-MIGRATION-MATRIX.md |
| Canonical repo 判定表 | docs/security/SOURCE-CONTROL-CANONICAL-DECISION-TABLE.md |
| GitHub target 決策表 | docs/security/GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md |
| GitHub target 決策 JSON | docs/security/github-target-decision.snapshot.json |
| GitHub target owner decision response 收件包 | docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md |
| GitHub target owner decision response JSON | docs/security/github-target-owner-decision-response.snapshot.json |
| GitHub target repo approval package | docs/security/GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md |
| GitHub target repo approval JSON | docs/security/github-target-repo-approval-package.snapshot.json |
| Source Control approval board | docs/security/SOURCE-CONTROL-APPROVAL-BOARD.md |
| Source Control approval board JSON | docs/security/source-control-approval-board.snapshot.json |
| Source Control draft reconcile plan | docs/security/SOURCE-CONTROL-RECONCILE-PLAN.md |
| Source Control draft reconcile plan JSON | docs/security/source-control-reconcile-plan.snapshot.json |
| Source Control branch/tag detail diff | docs/security/SOURCE-CONTROL-REF-DETAIL-DIFF.md |
| Source Control branch/tag detail diff JSON | docs/security/source-control-ref-detail-diff.snapshot.json |
| Source Control ref truth classification | docs/security/SOURCE-CONTROL-REF-TRUTH-CLASSIFICATION.md |
| Source Control ref truth classification JSON | docs/security/source-control-ref-truth-classification.snapshot.json |
| Source Control ref truth owner response 收件包 | docs/security/SOURCE-CONTROL-REF-TRUTH-OWNER-RESPONSE.md |
| Source Control ref truth owner response JSON | docs/security/source-control-ref-truth-owner-response.snapshot.json |
| Source Control GitHub primary readiness gate | docs/security/SOURCE-CONTROL-PRIMARY-READINESS-GATE.md |
| Source Control GitHub primary readiness gate JSON | docs/security/source-control-primary-readiness-gate.snapshot.json |
| Source Control GitHub primary rollback ADR | docs/security/SOURCE-CONTROL-PRIMARY-ROLLBACK-ADR.md |
| Source Control GitHub primary rollback ADR JSON | docs/security/source-control-primary-rollback-adr.snapshot.json |
| Source Control workflow / secret name inventory | docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-INVENTORY.md |
| Source Control workflow / secret name inventory JSON | docs/security/source-control-workflow-secret-name-inventory.snapshot.json |
| Source Control workflow / secret name local evidence | docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-LOCAL-EVIDENCE.md |
| Source Control workflow / secret name local evidence JSON | docs/security/source-control-workflow-secret-name-local-evidence.snapshot.json |
| Source Control workflow / secret name local collector | scripts/security/source-control-workflow-secret-name-local-inventory.py |
| Source Control workflow / secret name export request | docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md |
| Source Control workflow / secret name export request JSON | docs/security/source-control-workflow-secret-name-export-request.snapshot.json |
| Source Control workflow / secret name owner response 收件包 | docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md |
| Source Control workflow / secret name owner response JSON | docs/security/source-control-workflow-secret-name-owner-response.snapshot.json |
| Source Control owner response validation rollup | docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md |
| Source Control owner response validation rollup JSON | docs/security/source-control-owner-response-validation-rollup.snapshot.json |
| Kali 112 integration status | docs/security/KALI-INTEGRATION-STATUS.md |
| Kali 112 integration status JSON | docs/security/kali-integration-status.snapshot.json |
| Security finding contract | docs/security/SECURITY-FINDING-CONTRACT.md |
| Security finding sample JSON | docs/security/security-finding-kali-sample.snapshot.json |
| Kali scan scope approval package | docs/security/KALI-SCAN-SCOPE-APPROVAL-PACKAGE.md |
| Kali scan scope approval JSON | docs/security/kali-scan-scope-approval.snapshot.json |
| Security approval queue | docs/security/SECURITY-APPROVAL-QUEUE.md |
| Security approval queue JSON | docs/security/security-approval-queue.snapshot.json |
| Security approval gate | docs/security/SECURITY-APPROVAL-GATE.md |
| Security approval gate JSON | docs/security/security-approval-gate.snapshot.json |
| Security approval decision record | docs/security/SECURITY-APPROVAL-DECISION-RECORD.md |
| Security approval decision record JSON | docs/security/security-approval-decision-record.snapshot.json |
| Security approval review packet | docs/security/SECURITY-APPROVAL-REVIEW-PACKET.md |
| Security approval review packet JSON | docs/security/security-approval-review-packet.snapshot.json |
| Security approval state transition | docs/security/SECURITY-APPROVAL-STATE-TRANSITION.md |
| Security approval state transition JSON | docs/security/security-approval-state-transition.snapshot.json |
| Security follow-up runtime gate preparation | docs/security/SECURITY-FOLLOWUP-RUNTIME-GATE.md |
| Security follow-up runtime gate preparation JSON | docs/security/security-followup-runtime-gate.snapshot.json |
| Security mirror readiness | docs/security/SECURITY-MIRROR-READINESS.md |
| Security mirror readiness JSON | docs/security/security-mirror-readiness.snapshot.json |
| Security mirror intake plan | docs/security/SECURITY-MIRROR-INTAKE-PLAN.md |
| Security mirror intake plan JSON | docs/security/security-mirror-intake-plan.snapshot.json |
| 資安鏡像事件契約 | docs/security/SECURITY-MIRROR-EVENT-CONTRACT.md |
| 資安鏡像事件範例 JSON | docs/security/security-mirror-event-sample.snapshot.json |
| 資安鏡像路由矩陣 | docs/security/SECURITY-MIRROR-ROUTE.md |
| 資安鏡像路由矩陣 JSON | docs/security/security-mirror-route.snapshot.json |
| 資安鏡像驗收契約 | docs/security/SECURITY-MIRROR-ACCEPTANCE.md |
| 資安鏡像驗收契約 JSON | docs/security/security-mirror-acceptance.snapshot.json |
| 資安鏡像隔離契約 | docs/security/SECURITY-MIRROR-QUARANTINE.md |
| 資安鏡像隔離契約 JSON | docs/security/security-mirror-quarantine.snapshot.json |
| 資安鏡像 dry-run 報告契約 | docs/security/SECURITY-MIRROR-DRY-RUN.md |
| 資安鏡像 dry-run 報告契約 JSON | docs/security/security-mirror-dry-run.snapshot.json |
| 資安鏡像狀態彙整契約 | docs/security/SECURITY-MIRROR-STATUS-ROLLUP.md |
| 資安鏡像狀態彙整契約 JSON | docs/security/security-mirror-status-rollup.snapshot.json |
| 低摩擦 rollout policy | docs/security/SECURITY-LOW-FRICTION-ROLLOUT-POLICY.md |
| 低摩擦 rollout policy JSON | docs/security/security-rollout-policy.snapshot.json |
| Security Supply Chain contract manifest | docs/security/SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md |
| Security Supply Chain contract manifest JSON | docs/security/security-supply-chain-contract-manifest.snapshot.json |
2. 現在不能做的事
- 不建立或刪除 GitHub / Gitea repo。
- 不修改 repo visibility。
- 不同步 refs、branch、tag。
- 不切 GitHub primary。
- 不把 Codex patch runner、Kali scan 或 deploy 接進 AwoooP runtime。
- 不保存 secret / token value。
2.1 初期不要過度收緊
- Read-only inventory、文件化、risk label、mirror evidence 可持續推進。
- 初期不把 LOW / MEDIUM observation 變成阻擋條件。
- 缺 owner response、partial mirror、source-control drift、Kali observe finding、workflow / secret name gap 或 headline holding 初期只建立 follow-up / owner review，不直接變 runtime blocker。
- 初期不要求所有 repo 一次完成最高等級 controls。
- 只針對不可逆或高風險動作設 approval gate。
- 每階段完成後再逐步收斂，避免讓產品、架構與部署流程突然變複雜。
3. 下一階段建議
- 先依 S4.9
GITEA-INVENTORY-OWNER-ATTESTATION-RESPONSE.md收到並驗收 S4.7GITEA-INVENTORY-COVERAGE-ATTESTATION.md的 owner response；S4.8 已把這件事接到既有 approval queue / gate / review packet / follow-up runtime gate。之後再依 S4.5GITEA-AUTHENTICATED-INVENTORY-EXPORT-REQUEST.md取得 Gitea 認證清冊；收到 payload 後依 S4.6GITEA-AUTHENTICATED-INVENTORY-IMPORT-ACCEPTANCE.md驗收 / 拒收 / 隔離。目前未認證公開範圍 2 個、本機可見 Gitea unique 4 個、覆蓋缺口 2 個、attestation items 5 個、owner response 0 筆；只能用只讀 token API 或已脫敏管理匯出補私有 / 內部 server-side 全量 repo list，不保存 token value。 - 依 S4.10
GITHUB-TARGET-OWNER-DECISION-RESPONSE.mdrequest packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 與SOURCE-CONTROL-APPROVAL-BOARD.md對 7 個approval_required=true的 GitHub target 做 owner / visibility / canonical response；目前 response 0 筆、accepted 0 筆，通過後也只更新 read-only decision table / approval package / readiness gate，不代表 repo creation、visibility change、refs sync 或 primary approval。 - 依 S4.11
SOURCE-CONTROL-REF-TRUTH-OWNER-RESPONSE.mdrequest packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與SOURCE-CONTROL-REF-TRUTH-CLASSIFICATION.md對awoooi、clawbot-v5、wooo-aiops做單 repo / 單 ref owner response 驗收；audit event templates 目前 0 emitted，redaction examples 只示範安全 metadata shape，collection checks 只維持 request / received / accepted 分離，preflight 只分類可審、補證、隔離、拒收或等待，response 通過也只更新 read-only classification / reconcile / readiness wording，仍不得 push/delete refs 或 force push。 - 依 S4.12
SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.mdrequest packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 與SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md對 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 做 owner response 驗收；request packet 只顯示要回覆欄位與拒收 payload，template status ledger 只顯示 waiting，audit event templates 只定義 0 emitted 的脫敏 metadata，redaction examples 只示範安全 metadata shape，collection checks 只維持 request / received / accepted 分離，preflight 只分類可審、補證、隔離或拒收，不代表已送出、已收到、已接受或 production ingestion，response 通過也只更新 read-only inventory / export request / readiness wording，仍不得收 secret value、改 workflow 或啟用 runner。 - 依 S4.13
SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md集中檢查 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets、evidence routing rules、display sections、state transition rules、reviewer checklist、reviewer outcome lanes、reviewer audit event templates、reviewer audit display sections、reviewer audit collection checks、reviewer audit redaction examples、reviewer audit retention rules、reviewer audit retention checks、reviewer audit handoff packets、handoff checks、parallel session sync checks、parallel session conflict lanes、parallel session recovery checks 與 parallel session recovery outcome lanes；rollup / routing / sections / transition rules / checklist / outcome lanes / audit templates / audit display sections / audit collection checks / audit redaction examples / audit retention rules / audit retention checks / audit handoff packets / handoff checks / parallel session sync checks / parallel session conflict lanes / parallel session recovery checks / parallel session recovery outcome lanes 通過也只更新 read-only wording，不代表 approval、production ingestion 或 execution authorization。 - 對
ewoooc/momo-pro-system完成 server-side canonical 判定。 - 依
KALI-SCAN-SCOPE-APPROVAL-PACKAGE.md取得 safe crawl、credentialed scan、runtime ingestion、full-upgrade / reboot 等 gate 的人工批准；不得直接接/execute。 - AwoooP 主線先讀
security_mirror_readiness_v1、security_mirror_intake_plan_v1、security_mirror_event_v1、security_mirror_route_v1、security_mirror_acceptance_v1、security_mirror_quarantine_v1、security_mirror_dry_run_v1、security_mirror_status_rollup_v1、S4.13source_control_owner_response_validation_rollup_v1、security_approval_gate_v1、security_approval_decision_record_v1、security_approval_review_packet_v1、security_approval_state_transition_v1、security_followup_runtime_gate_v1、source_control_primary_readiness_gate_v1、source_control_primary_rollback_adr_v1與source_control_workflow_secret_name_inventory_v1，只建立 mirror-only / read-only policy 入口，不新增執行按鈕；其中 S4.13 需顯示四包 owner response validation rollup、missing lanes、collection order、next collection candidate、evidence routing rules、display sections、state transition rules、reviewer checklist、reviewer outcome lanes、reviewer audit event templates、reviewer audit display sections、reviewer audit collection checks、reviewer audit redaction examples、reviewer audit retention rules、reviewer audit retention checks、reviewer audit handoff packets、handoff checks、parallel session sync checks、parallel session conflict lanes、parallel session recovery checks 與 parallel session recovery outcome lanes，Gitea inventory 需同時顯示 S4.5 認證清冊匯出請求、S4.6 匯入驗收契約、S4.7 owner coverage attestation 與 S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / 收件包，GitHub target 決策需同時顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 owner decision response templates，refs truth 需同時顯示 S4.11 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 templates，workflow / secret inventory 需同時顯示 S4.3 redacted export request、S4.12 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 5 個 owner response templates，primary readiness 需同時顯示 S4.4 rollback ADR 草案。 - AwoooP 主線消費
security_rollout_policy_v1時，只做 read-only policy，不做 runtime blocking；7 條 non-blocking escalation lanes 只能顯示、建立 follow-up 或要求 owner review before blocking。 - AwoooP 主線再讀
security_approval_queue_v1、security_approval_gate_v1、security_approval_decision_record_v1、security_approval_review_packet_v1、security_approval_state_transition_v1、security_followup_runtime_gate_v1、source_control_primary_readiness_gate_v1、source_control_primary_rollback_adr_v1、source_control_workflow_secret_name_inventory_v1與security_supply_chain_contract_manifest_v1，顯示 review order、批准範圍、審查封包、決策紀錄、決策後狀態、後續 runtime gate 準備條件、Gitea inventory 覆蓋缺口、S4.5 認證匯出請求、S4.6 匯入驗收 / 隔離規則、S4.7 owner attestation items、S4.9 owner response request packet、S4.9 owner response template status ledger、S4.9 owner response audit event templates、S4.9 owner response redaction examples、S4.9 owner response display sections、S4.9 owner response collection checks、S4.9 owner response templates、S4.10 GitHub target owner response request packet、S4.10 GitHub target owner response template status ledger、S4.10 GitHub target owner response audit event templates、S4.10 GitHub target owner response redaction examples、S4.10 GitHub target owner response collection checks、S4.10 GitHub target owner response intake preflight checks、S4.10 GitHub target owner response templates、S4.11 refs truth owner response request packet、S4.11 refs truth owner response template status ledger、S4.11 refs truth owner response audit event templates、S4.11 refs truth owner response redaction examples、S4.11 refs truth owner response collection checks、S4.11 refs truth owner response intake preflight checks、S4.11 refs truth owner response templates、S4.12 workflow / secret 名稱 owner response request packet、S4.12 workflow / secret 名稱 owner response template status ledger、S4.12 workflow / secret 名稱 owner response audit event templates、S4.12 workflow / secret 名稱 owner response redaction examples、S4.12 workflow / secret 名稱 owner response collection checks、S4.12 workflow / secret 名稱 owner response intake preflight checks、S4.12 workflow / secret 名稱 owner response templates、S4.13 owner response validation rollup、evidence routing rules、display sections、state transition rules、reviewer checklist、reviewer outcome lanes、reviewer audit event templates、reviewer audit display sections、reviewer audit collection checks、reviewer audit redaction examples、reviewer audit retention rules、reviewer audit retention checks、reviewer audit handoff packets、reviewer audit handoff checks、parallel session sync checks、parallel session conflict lanes、parallel session recovery checks 與 parallel session recovery outcome lanes、S1.3 non-blocking escalation lanes、GitHub primary readiness blockers、rollback ADR 草案、workflow / secret 名稱 inventory 缺口、redacted export request 與 blocked reason，不新增 execution router。