docs(security): refresh IwoooS source control readiness [skip ci]
This commit is contained in:
@@ -9,7 +9,7 @@
|
||||
| 工作視窗 | IwoooS / AWOOOI 資安治理 P0 |
|
||||
| 本次乾淨 worktree | `/private/tmp/awoooi-iwooos-governance-p0-20260604` |
|
||||
| 本次分支 | `codex/iwooos-governance-p0-20260604` |
|
||||
| 最新觀察到的 `gitea/main` | `0260ec89 chore(cd): deploy 973fc7a [skip ci]` |
|
||||
| 最新觀察到的 `gitea/main` | `6efbd7c6 chore(cd): deploy 1ae8f80 [skip ci]` |
|
||||
| 前一個正式 IwoooS 候選基準 | code `7b8fc093`、deploy marker `45c63488`、LOGBOOK `02cadee6` |
|
||||
| 最新導航 IA 基準 | code `973fc7a4`、LOGBOOK `2555c811`、deploy marker `0260ec89` |
|
||||
| 禁止事項 | 不 force push、不 destructive git、不 SSH 修改主機、不 active scan、不收 secrets 明文、不把 AwoooP approval 當資安批准、不把 UI 可見當 runtime 授權 |
|
||||
@@ -23,7 +23,7 @@
|
||||
| runtime landing | 40-45% | 否 | production 只讀頁存在,不等於 runtime ingestion 或 execution router |
|
||||
| active runtime gate | 0 | 否 | 必須維持 0,直到獨立人工批准、rollback、post-check 與 guard 成立 |
|
||||
| S4.9 owner response gate | 0% | 可在收到合格回覆後調整 | 目前只定義欄位、預檢、收件與驗收,不標記 received / accepted |
|
||||
| GitHub primary readiness | 0 | 否 | 目前只讀盤點,不建立 repo、不同步 refs、不切 primary |
|
||||
| GitHub primary readiness | 0 | 否 | primary gate 仍為 0;P1 只讀重盤工作本身目前約 55%,不代表可切 primary |
|
||||
| Kali 112 維護準備 | 只讀證據已納管,維護尚未開始 | 否 | 不更新套件、不重啟、不 hardening、不 active scan |
|
||||
| 111 / 168 開發主機納管 | observe-only mapping 已有,維護包需補強 | 可補文件,不調 runtime | 仍不 credentialed scan、不讀未授權資料、不自動修復 |
|
||||
| VibeWork 納入 IwoooS | 前端態勢已有 onboarding 欄位,產品邊界需補規範 | 可補文件 | 保留 VibeWork 獨立產品邊界 |
|
||||
@@ -114,6 +114,53 @@ S4.9 是目前 IwoooS 64% 能往前的第一優先 gate。驗收前所有 count
|
||||
| P3 | AI Agent 評估 | NemoTron / Hermes / OpenClaw / ElephantAlpha dry-run、benchmark、成本、安全邊界 | 不切 production |
|
||||
| P3 | runtime gate 收斂 | owner evidence、人工批准、rollback、disable、post-check | production truth,不只 UI |
|
||||
|
||||
## 6.1 P1 GitHub Primary Readiness 只讀重盤狀態
|
||||
|
||||
本階段只處理 evidence freshness 與規範落差,不切 GitHub primary、不建立 repo、不同步 refs、不改 workflow、不收 secret value。GitHub primary readiness gate 仍維持 `0`。
|
||||
|
||||
| 工作 | 完成度 | 2026-06-04 結果 | 下一步 |
|
||||
|------|--------|-----------------|--------|
|
||||
| `awoooi` Gitea / GitHub refs refresh | 100% | Gitea heads `170`、GitHub heads `2`、Gitea tags `2`、GitHub tags `0`、main SHA 不一致 | 重產 ref detail diff / ref truth classification |
|
||||
| Gitea public repo inventory refresh | 100% | user endpoint public-only 仍只見 `wooo/awoooi`、`wooo/ewoooc`;org endpoint 仍 blocked / 404 | 取得只讀 token 或 redacted admin export 批准 |
|
||||
| GitHub target probe refresh | 100% | 8 個候選中 5 個可讀、3 個 `not_found_or_private`;`open-design` heads `644` 只作 external scope evidence | owner / visibility / canonical response 仍待收 |
|
||||
| Workflow / secret 名稱本機 evidence refresh | 100% | 31 個 workflow files、42 個 unique referenced secret names、`secret_value_detected=false` | 補 webhook、runner owner、deploy key、branch protection、secret name parity |
|
||||
| Primary readiness gate 文件更新 | 80% | 已寫入 2026-06-04 refresh 與禁止誤讀規則 | 跑 guard 後以 LOGBOOK 封存 |
|
||||
| 全量 Gitea 專案版本盤點 | 25% | 目前仍是 public-only + 本機輔助 evidence | 需只讀 token / admin export;不使用 write credential |
|
||||
| 逐 repo refs truth queue | 20% | 舊 S4.11 `141` refs review items 已落後於 current `170` heads | 先重產 queue,再送 owner response |
|
||||
| Workflow / runner / secret parity owner response | 15% | 有 local evidence 與 template,但 received / accepted 皆 0 | 只收 redacted metadata,不收 value |
|
||||
| GitHub primary cutover readiness | 0% | `primary_ready_count=0`、`github_primary_switch_authorized=false` | 需 owner、parity、rollback ADR、人工批准全部成立 |
|
||||
|
||||
P1 只讀重盤階段整體完成度:`55%`。它代表 freshness / inventory 工作進度,不代表 GitHub primary gate 或 runtime gate 提升。
|
||||
|
||||
## 6.2 規範分析:已不符合、需新增、需調整
|
||||
|
||||
| 分類 | 項目 | 原因 | 本輪處理 |
|
||||
|------|------|------|----------|
|
||||
| 已不符合現在要求 | `GITEA-GITHUB-MIGRATION-INVENTORY.md` 仍寫 2026-05-12 / 117 heads / 舊 main SHA | 2026-06-04 refresh 顯示 Gitea heads `170`、main SHA `6efbd7c6...` | 已更新為第三版 read-only inventory refresh |
|
||||
| 已不符合現在要求 | S4.11 `141` refs review items 被當成 current queue | current `awoooi` Gitea heads 已增至 `170` | 已標記需重產 ref detail diff / ref truth classification |
|
||||
| 已不符合現在要求 | Workflow local evidence 指到舊暫存 worktree | 舊路徑不可重現,會污染 P1 evidence freshness | 已改為本輪乾淨 worktree,並新增 snapshot freshness 規則 |
|
||||
| 已不符合現在要求 | `SOURCE-CONTROL-PRIMARY-READINESS-GATE.md` 日期停在 2026-05-17 | Gate 內容未反映最新 refs / GitHub target / workflow evidence | 已新增 2026-06-04 P1 只讀重盤結論 |
|
||||
| 需要新增規範 | Generator output 與人工治理註記分層 | `GITEA-REPO-INVENTORY-SNAPSHOT.md` 重產時會覆蓋 S4.5 / S4.6 / S4.7 補註 | 已補回註記,並列為後續 generator / governance 分層工作 |
|
||||
| 需要新增規範 | External / high-churn repo evidence 摘要規則 | `nexu-io/open-design` heads `644`,不宜把外部 refs 全量混入 AWOOOI primary readiness | 已標記只作 external scope summary,不納入 cutover queue |
|
||||
| 需要新增規範 | P1 page verification decision rule | 文件 / snapshot 更新不一定需要開頁;若宣稱 production 狀態或改前端才必須開頁 | 已保留驗證節點規則,本階段不改前端、不宣稱新 production |
|
||||
| 需要調整規範 | GitHub target probe wording | `not_found_or_private` 容易被誤讀成不存在 | 已在 primary gate 重申不可自動建立 repo、不可切 primary |
|
||||
| 需要調整規範 | Workflow / secret 名稱完成度 | local evidence 已有,但 webhook / runner / deploy key / branch protection / parity 仍缺 | 已改為 `missing_evidence`,不得說已完成 parity |
|
||||
| 需要調整規範 | AwoooP 同步封包 | P1 要同步 refreshed counts、blocked gates、no-run 狀態,避免另一 Session 以舊 117 heads 繼續推進 | 本總帳與 LOGBOOK 會作為同步封包來源 |
|
||||
|
||||
## 6.3 P1 優先順序細化
|
||||
|
||||
| 優先 | 工作 | 內容 | 完成條件 |
|
||||
|------|------|------|----------|
|
||||
| P1-1 | Source-control refs truth 重產 | 以 2026-06-04 `awoooi` refs refresh 重產 detail diff / truth classification | 新 queue 不再引用舊 `141` 為 current |
|
||||
| P1-2 | Gitea authenticated inventory request | 依 S4.5/S4.6/S4.7/S4.9 收只讀 token 或 redacted admin export | 只收 metadata,不保存 token value |
|
||||
| P1-3 | GitHub target owner response | 對 7 個 in-scope targets 收 owner / visibility / canonical 決策 | received / accepted 前仍全部 0 |
|
||||
| P1-4 | Workflow / runner / secret parity evidence | webhook、runner owner、deploy key、branch protection、CODEOWNERS、secret name parity | redacted evidence refs 完整,secret value 仍拒收 |
|
||||
| P1-5 | Primary rollback ADR 補強 | 逐 repo rollback owner、trigger、validation window、fallback role | ADR approved 前不切 primary |
|
||||
| P1-6 | AwoooP Session 同步 | 同步 commits、runs、production sanity、P1 refresh counts、gate 0 / false | 另一 Session 不再使用舊 refs count |
|
||||
| P1-7 | Kali 112 maintenance window 草案 | packages、`networking.service` failed、hardening 0/4、rollback、post-check | 文件草案,不執行 `apt upgrade` / restart / scan |
|
||||
| P1-8 | 111 / 168 開發主機 scope | scope、credential handling、rollback owner、validation 指標 | observe-only,不做 credentialed scan |
|
||||
| P1-9 | VibeWork 納入 IwoooS | repo / product / surface / owner / evidence refs / 獨立產品邊界 | docs/specs 繁中,產品責任不合併 |
|
||||
|
||||
## 7. 2026-06-04 本輪驗證紀錄
|
||||
|
||||
| 驗證 | 結果 |
|
||||
|
||||
Reference in New Issue
Block a user