From 446a7ac5aef20c3e2f971a0ec396793cfae899c5 Mon Sep 17 00:00:00 2001 From: Your Name Date: Mon, 18 May 2026 15:41:31 +0800 Subject: [PATCH] docs(security): add github target owner redaction examples --- docs/LOGBOOK.md | 15 ++ ...get_owner_decision_response_v1.schema.json | 37 +++++ ...WOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md | 6 +- ...ECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md | 8 +- .../GITHUB-TARGET-OWNER-DECISION-RESPONSE.md | 26 ++- .../GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md | 2 +- ...GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md | 2 +- docs/security/SECURITY-APPROVAL-GATE.md | 2 +- docs/security/SECURITY-APPROVAL-QUEUE.md | 2 +- .../SECURITY-APPROVAL-REVIEW-PACKET.md | 2 +- .../SECURITY-FOLLOWUP-RUNTIME-GATE.md | 2 +- docs/security/SECURITY-MIRROR-DRY-RUN.md | 2 +- docs/security/SECURITY-MIRROR-READINESS.md | 2 +- .../security/SECURITY-MIRROR-STATUS-ROLLUP.md | 4 +- ...SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md | 4 +- .../SECURITY-SUPPLY-CHAIN-PROGRESS.md | 10 +- .../security/SOURCE-CONTROL-APPROVAL-BOARD.md | 2 +- ...ONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md | 2 +- .../SOURCE-CONTROL-PRIMARY-READINESS-GATE.md | 8 +- ...rget-owner-decision-response.snapshot.json | 153 ++++++++++++++++++ .../security-approval-gate.snapshot.json | 4 +- .../security-approval-queue.snapshot.json | 6 +- ...urity-approval-review-packet.snapshot.json | 4 +- ...curity-followup-runtime-gate.snapshot.json | 4 +- .../security-mirror-dry-run.snapshot.json | 2 +- .../security-mirror-readiness.snapshot.json | 4 +- ...ecurity-mirror-status-rollup.snapshot.json | 10 +- ...pply-chain-contract-manifest.snapshot.json | 4 +- ...ource-control-approval-board.snapshot.json | 2 +- ...r-response-validation-rollup.snapshot.json | 2 +- ...ntrol-primary-readiness-gate.snapshot.json | 4 +- .../source-control-owner-response-guard.py | 7 + 32 files changed, 286 insertions(+), 58 deletions(-) diff --git a/docs/LOGBOOK.md b/docs/LOGBOOK.md index 01abf1a6a..fefa3f8c5 100644 --- a/docs/LOGBOOK.md +++ b/docs/LOGBOOK.md @@ -1,3 +1,18 @@ +## 2026-05-18 | 資安供應鏈 S4.10：GitHub Target Owner Response Redaction Examples + +**背景**：S4.10 已有 owner response request packet、7 個 template status ledger 與 3 個 audit event templates；本輪補上 5 個 redaction examples，讓 AwoooP / owner 知道如何用脫敏 metadata 回覆 GitHub target owner / visibility / canonical 決策，避免把 token、private clone URL credential、API raw body、repo archive、git object pack 或 refs 執行指令貼進 response。 + +**完成**： +- `github_target_owner_decision_response_v1` schema 新增 optional `owner_response_redaction_examples`，summary 新增 `owner_response_redaction_example_count=5`。 +- `github-target-owner-decision-response.snapshot.json` 新增 5 個 redaction examples，全部維持 `template_example_only`、`stored_raw_payload_allowed=false`、`execution_authorized=false` 與 `not_approval=true`。 +- `source-control-owner-response-guard.py` 反查 S4.10 redaction example count、example id 順序、display order、狀態、raw payload 儲存禁令與 approval / execution 禁令。 +- 更新 S4.10 人讀文件與 AwoooP / readiness / approval / status rollup / manifest / progress 顯示說明。 + +**仍禁止**： +- 不把 S4.10 redaction examples 當成 owner response received、accepted 或 AwoooP production ingestion。 +- 不保存 owner response raw body、token value、secret value、private clone URL credential、API request/response body、repo archive、git object pack、DB dump 或 execution request payload。 +- 不讓 redaction examples 觸發 repo creation、visibility change、refs sync、delete refs、force push、GitHub primary switch、workflow / secret / runner 變更或任何 runtime action。 + ## 2026-05-18 | 資安供應鏈 S4.10：GitHub Target Owner Response Audit Event Templates **背景**：S4.10 已有 owner response request packet 與 7 個 template status ledger；本輪補上 3 個 audit event templates，讓 AwoooP 未來可以用固定格式顯示 request shown、response received metadata、outcome classified 的稽核 metadata，但仍不啟用 production ingestion。 diff --git a/docs/schemas/github_target_owner_decision_response_v1.schema.json b/docs/schemas/github_target_owner_decision_response_v1.schema.json index d168fcfd8..379e72ce6 100644 --- a/docs/schemas/github_target_owner_decision_response_v1.schema.json +++ b/docs/schemas/github_target_owner_decision_response_v1.schema.json @@ -61,6 +61,7 @@ "owner_response_request_packet_count", "owner_response_template_status_count", "owner_response_audit_event_template_count", + "owner_response_redaction_example_count", "response_template_count", "received_response_count", "accepted_response_count", @@ -84,6 +85,7 @@ "owner_response_request_packet_count": {"type": "integer", "minimum": 0}, "owner_response_template_status_count": {"type": "integer", "minimum": 0}, "owner_response_audit_event_template_count": {"type": "integer", "minimum": 0}, + "owner_response_redaction_example_count": {"type": "integer", "minimum": 0}, "response_template_count": {"type": "integer", "minimum": 0}, "received_response_count": {"type": "integer", "minimum": 0}, "accepted_response_count": {"type": "integer", "minimum": 0}, @@ -244,6 +246,41 @@ }, "minItems": 1 }, + "owner_response_redaction_examples": { + "type": "array", + "description": "Owner 回覆 S4.10 GitHub target owner decision 時可參考的脫敏範例；只供 AwoooP 顯示，不代表收件、驗收或執行授權。", + "items": { + "type": "object", + "required": [ + "example_id", + "display_order", + "example_status", + "category", + "safe_response_shape", + "required_redactions", + "forbidden_raw_values", + "stored_raw_payload_allowed", + "awooop_display_mode", + "execution_authorized", + "not_approval" + ], + "properties": { + "example_id": {"type": "string"}, + "display_order": {"type": "integer", "minimum": 1}, + "example_status": {"type": "string", "enum": ["template_example_only"]}, + "category": {"type": "string"}, + "safe_response_shape": {"type": "array", "items": {"type": "string"}, "minItems": 1}, + "required_redactions": {"type": "array", "items": {"type": "string"}, "minItems": 1}, + "forbidden_raw_values": {"type": "array", "items": {"type": "string"}, "minItems": 1}, + "stored_raw_payload_allowed": {"type": "boolean", "const": false}, + "awooop_display_mode": {"type": "string", "enum": ["display_redaction_example_only"]}, + "execution_authorized": {"type": "boolean", "const": false}, + "not_approval": {"type": "boolean", "const": true} + }, + "additionalProperties": false + }, + "minItems": 1 + }, "response_templates": { "type": "array", "items": { diff --git a/docs/security/AWOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md b/docs/security/AWOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md index 7616467dc..78f1bd91c 100644 --- a/docs/security/AWOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md +++ b/docs/security/AWOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md @@ -48,8 +48,8 @@ AwoooP 初期不得直接啟動掃描、不得呼叫 Codex patch runner、不得 | `gitea_repo_inventory_v1` | Gitea org/user repo list 或管理匯出 | Supply-chain evidence、migration matrix | mirror-only | 顯示 public-only evidence、S4.5 authenticated/admin export request、S4.6 redacted import acceptance、S4.7 owner coverage attestation、S4.9 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、owner response 收件包、6 個 intake preflight checks 與 5 個 outcome lanes；不保存 token value、不刪除或停用 Gitea repo | | `local_git_remote_inventory_v1` | 本機可見 Git working tree remote | Source-control coverage evidence、migration matrix | mirror-only | 不視為 Gitea server 全量、不修改 remote | | `github_target_probe_v1` | 候選 GitHub repo read-only probe | Migration target evidence | mirror-only | `not_found_or_private` 不等同確認不存在 | -| `github_target_decision_v1` | GitHub target 建立與可見性決策草案；S4.10 owner decision response request packet / 收件包 | Approval candidate、Migration target evidence | mirror-only | approval 前不得建立 repo、修改 visibility、同步 refs；S4.10 request packet 只顯示 7 個 target 要求，template status ledger 逐項顯示 waiting / request ready，audit event templates 只定義 0 emitted 的脫敏 metadata，response 目前 0 筆，不代表執行批准 | -| `github_target_repo_approval_package_v1` | GitHub target 逐 repo approval package；S4.10 request packet / template status ledger / audit event templates / response templates | Approval queue、Migration target evidence | mirror-only | 低摩擦，只 gate 高風險執行；request packet 只顯示 owner 要回覆什麼，response 通過也只更新 read-only evidence | +| `github_target_decision_v1` | GitHub target 建立與可見性決策草案；S4.10 owner decision response request packet / 收件包 | Approval candidate、Migration target evidence | mirror-only | approval 前不得建立 repo、修改 visibility、同步 refs；S4.10 request packet 只顯示 7 個 target 要求，template status ledger 逐項顯示 waiting / request ready，audit event templates 只定義 0 emitted 的脫敏 metadata，redaction examples 只顯示可接受的脫敏 metadata shape，response 目前 0 筆，不代表執行批准 | +| `github_target_repo_approval_package_v1` | GitHub target 逐 repo approval package；S4.10 request packet / template status ledger / audit event templates / redaction examples / response templates | Approval queue、Migration target evidence | mirror-only | 低摩擦，只 gate 高風險執行；request packet 只顯示 owner 要回覆什麼，response 通過也只更新 read-only evidence | | `source_control_approval_board_v1` | 逐 repo owner / visibility / canonical / refs 決策 board | Approval queue、PR reviewer handoff | approval-only | 只顯示決策隊列，不執行 board item | | `source_control_reconcile_plan_v1` | refs-blocked repo draft reconcile plan | Approval candidate、migration reviewer handoff | approval-only | 只顯示草案；S4.11 response 通過前只更新 wording，不 push refs、不切 primary | | `source_control_ref_detail_diff_v1` | refs-blocked repo branch/tag 明細 diff | Migration reviewer evidence | mirror-only | 只顯示 diff，不 fetch、不 push、不刪 refs | @@ -123,7 +123,7 @@ AwoooP 初期不得直接啟動掃描、不得呼叫 Codex patch runner、不得 | `approval_required_event_v1.requested_action=run_gitea_readonly_inventory` | `approve_required` | 只允許 read-only token 或 redacted admin export，不保存 token value | | `local_git_remote_inventory_v1.status=partial` | `observe` | 補 server-side inventory，不做主控切換 | | `github_target_probe_v1.status=ok` 且有 `not_found_or_private` | `observe` | 補 GitHub target 決策，不自動建立 repo | -| `github_target_decision_v1.approval_required_count>0` | `approve_required` | 產生 approval candidate，並顯示 S4.10 owner response request packet、template status ledger、audit event templates 與 owner decision response templates；不執行 repo 建立、visibility 修改、refs sync 或 primary switch | +| `github_target_decision_v1.approval_required_count>0` | `approve_required` | 產生 approval candidate，並顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples 與 owner decision response templates；不執行 repo 建立、visibility 修改、refs sync 或 primary switch | | `github_target_repo_approval_package_v1.status=draft` | `observe` | 建立 approval queue draft，不阻擋 read-only evidence；S4.10 response 通過前不得視為 repo / visibility / refs 批准 | | `source_control_approval_board_v1.pending_approval_count>0` | `approve_required` | 顯示逐 repo 決策隊列，不執行 repo 建立、visibility 修改、refs sync | | `source_control_reconcile_plan_v1.status=draft_blocked` | `approve_required` | 只顯示 refs reconcile 草案與 gate，不執行 sync | diff --git a/docs/security/AWOOOP-SECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md b/docs/security/AWOOOP-SECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md index 213c0d7e0..e6ef39875 100644 --- a/docs/security/AWOOOP-SECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md +++ b/docs/security/AWOOOP-SECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md @@ -645,7 +645,7 @@ Schema：`docs/schemas/github_target_decision_v1.schema.json` } ``` -AwoooP 初期處理方式：作為 approval candidate 與 migration target evidence；需同時顯示 S4.10 owner response request packet、template status ledger、audit event templates、owner decision response templates、received_response_count=0 與 rejection rules；不得直接建立 GitHub repo、修改 visibility、同步 refs 或切 GitHub primary。 +AwoooP 初期處理方式：作為 approval candidate 與 migration target evidence；需同時顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、owner decision response templates、received_response_count=0 與 rejection rules；不得直接建立 GitHub repo、修改 visibility、同步 refs 或切 GitHub primary。 ### `github_target_owner_decision_response_v1` @@ -668,7 +668,7 @@ Schema：`docs/schemas/github_target_owner_decision_response_v1.schema.json` } ``` -AwoooP 初期處理方式：mirror 成 owner response request / status / review lane。request packet 只顯示要請 owner 回覆哪 7 個 target 與不得貼什麼，template status ledger 只逐項顯示 waiting / request ready，audit event templates 只定義 0 emitted 的脫敏 metadata；response 通過後只更新 read-only decision table、approval package、approval board 與 primary readiness gate；不得把 request packet、template status ledger、audit event templates 或 response packet 當成 repo creation、visibility change、refs sync 或 GitHub primary approval。 +AwoooP 初期處理方式：mirror 成 owner response request / status / review lane。request packet 只顯示要請 owner 回覆哪 7 個 target 與不得貼什麼，template status ledger 只逐項顯示 waiting / request ready，audit event templates 只定義 0 emitted 的脫敏 metadata；response 通過後只更新 read-only decision table、approval package、approval board 與 primary readiness gate；不得把 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo creation、visibility change、refs sync 或 GitHub primary approval。 ### `github_target_repo_approval_package_v1` @@ -687,7 +687,7 @@ Schema：`docs/schemas/github_target_repo_approval_package_v1.schema.json` } ``` -AwoooP 初期處理方式：mirror 成 approval queue draft，並連到 S4.10 request packet / template status ledger / audit event templates / response 收件包。低摩擦原則下，read-only evidence 不被阻擋；只有 repo creation、visibility change、refs sync、primary switch 等高風險執行才需要 approval。 +AwoooP 初期處理方式：mirror 成 approval queue draft，並連到 S4.10 request packet / template status ledger / audit event templates / redaction examples / response 收件包。低摩擦原則下，read-only evidence 不被阻擋；只有 repo creation、visibility change、refs sync、primary switch 等高風險執行才需要 approval。 ### `approval_required_event_v1` @@ -875,7 +875,7 @@ Console 初期不提供高風險執行按鈕。 2026-05-12 GitHub target repo-by-repo approval package 追加：已新增 `docs/schemas/github_target_repo_approval_package_v1.schema.json`、`docs/security/github-target-repo-approval-package.snapshot.json` 與 `docs/security/GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md`。7 個 approval-required targets 已拆成逐 repo pending package；依統帥提醒採低摩擦分階段，不把 read-only evidence 變成阻擋條件。 -2026-05-17 S4.10 GitHub target owner decision response 收件包追加，2026-05-18 補 request packet：已新增 `docs/schemas/github_target_owner_decision_response_v1.schema.json`、`docs/security/github-target-owner-decision-response.snapshot.json` 與 `docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md`。AwoooP 可顯示 1 個 owner response request packet、7 個 template statuses、3 個 audit event templates、7 個 response templates、8 個 acceptance checks 與 10 個 rejection rules；目前收到 response 0 筆、接受 0 筆，仍不得建立 repo、修改 visibility、sync refs、切 GitHub primary 或停用 Gitea。 +2026-05-17 S4.10 GitHub target owner decision response 收件包追加，2026-05-18 補 request packet、template status ledger、audit event templates 與 redaction examples：已新增 `docs/schemas/github_target_owner_decision_response_v1.schema.json`、`docs/security/github-target-owner-decision-response.snapshot.json` 與 `docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md`。AwoooP 可顯示 1 個 owner response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples、7 個 response templates、8 個 acceptance checks 與 10 個 rejection rules；目前收到 response 0 筆、接受 0 筆，仍不得建立 repo、修改 visibility、sync refs、切 GitHub primary 或停用 Gitea。 2026-05-12 低摩擦 rollout policy 追加：已新增 `docs/schemas/security_rollout_policy_v1.schema.json`、`docs/security/security-rollout-policy.snapshot.json` 與 `docs/security/SECURITY-LOW-FRICTION-ROLLOUT-POLICY.md`。AwoooP 初期應採 observe-first / mirror-only，不把 LOW / MEDIUM observation 變成 blocking controls。 diff --git a/docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md b/docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md index 466c0a78e..a432a9a60 100644 --- a/docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md +++ b/docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md @@ -29,6 +29,7 @@ S4.10 不是 repo creation approval、不是 visibility change approval、不是 | owner response request packet | 1 | | owner response template statuses | 7 | | owner response audit event templates | 3 | +| owner response redaction examples | 5 | | response templates | 7 | | 已收到 response | 0 | | 已接受 response | 0 | @@ -87,6 +88,20 @@ AwoooP 可用 `owner_response_audit_event_templates` 做未來 audit metadata 這 3 個 event templates 目前都是 `template_only_not_emitted`，`emitted_event_count=0`。它們不代表 AwoooP production ingestion 已啟用，也不保存 owner response raw body、token、secret、private clone URL credential、repo archive、git object pack、DB dump、API request body 或 execution request payload。 +## 1.4 Owner Response Redaction Examples + +S4.10 redaction examples 只讓 AwoooP / owner 知道「可以怎麼安全描述 GitHub target owner decision」，避免把 token、private clone URL credential、API raw body、repo archive、git object pack 或 refs 執行指令貼進 response。 + +| Example | 用途 | 狀態 | +|---------|------|------| +| `redaction-github-target-doc-ref` | 用既有決策表與 snapshot 引用 GitHub target / refs blocker evidence | `template_example_only` | +| `redaction-owner-visibility-canonical-metadata` | 示範只回覆 owner、visibility review owner、canonical source 與 follow-up owner metadata | `template_example_only` | +| `redaction-private-target-access-metadata` | 示範 private / new target 只提供 repo slug、access request status 與 owner metadata | `template_example_only` | +| `redaction-refs-truth-dependency-summary` | 示範用 S4.11 / S4.12 blocker summary 取代 refs sync / delete / force-push 指令 | `template_example_only` | +| `redaction-github-target-quarantine-pointer` | 示範疑似含敏感 payload 時只留下 quarantine pointer，不保存原文 | `template_example_only` | + +這 5 個 examples 都是 `template_example_only`，`stored_raw_payload_allowed=false`。它們不代表 owner response 已收到、已驗收或已批准；也不授權 repo creation、visibility change、refs sync、delete refs、force push、GitHub primary switch 或 GitHub/Gitea write。 + ## 2. Owner Response 必填欄位 每筆 response 至少要能回答： @@ -152,11 +167,12 @@ AwoooP 可用 `owner_response_audit_event_templates` 做未來 audit metadata 1. 顯示 1 個 owner response request packet。 2. 顯示 7 個 owner response template statuses。 3. 顯示 3 個 owner response audit event templates。 -4. 顯示 7 個 owner decision response templates。 -5. 顯示 acceptance checks 與 rejection rules。 -6. 在 owner response 到來後，只更新 read-only decision table、approval package、approval board、primary readiness gate 與 status rollup。 -7. 將不完整或可疑 response 放進 mirror quarantine。 -8. 持續顯示 `received_response_count=0`、`accepted_response_count=0`，直到真的收到脫敏 response。 +4. 顯示 5 個 owner response redaction examples。 +5. 顯示 7 個 owner decision response templates。 +6. 顯示 acceptance checks 與 rejection rules。 +7. 在 owner response 到來後，只更新 read-only decision table、approval package、approval board、primary readiness gate 與 status rollup。 +8. 將不完整或可疑 response 放進 mirror quarantine。 +9. 持續顯示 `received_response_count=0`、`accepted_response_count=0`，直到真的收到脫敏 response。 ## 8. AwoooP 不可做 diff --git a/docs/security/GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md b/docs/security/GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md index 096fb0f4c..8af252352 100644 --- a/docs/security/GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md +++ b/docs/security/GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md @@ -21,7 +21,7 @@ 這份 package 只讓 AwoooP / 統帥看到每個 repo 的批准條件與禁止動作，不代表已批准 push、mirror、repo creation、visibility 修改或 GitHub primary。 -S4.10 已補 1 個 owner response request packet、7 個 template statuses、3 個 audit event templates 與 7 個 owner decision response templates。owner response 通過後只允許更新 read-only decision table、approval package、approval board 與 primary readiness gate；它不等於 repo creation、visibility change、refs sync 或 primary approval。 +S4.10 已補 1 個 owner response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples 與 7 個 owner decision response templates。owner response 通過後只允許更新 read-only decision table、approval package、approval board 與 primary readiness gate；它不等於 repo creation、visibility change、refs sync 或 primary approval。 ## 0.1 低摩擦分階段原則 diff --git a/docs/security/GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md b/docs/security/GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md index 9cd165b37..ae0337c90 100644 --- a/docs/security/GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md +++ b/docs/security/GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md @@ -21,7 +21,7 @@ 因此現階段不得建立自動 mirror，也不得把 GitHub primary 視為 ready。 -S4.10 已補 owner decision response request packet、template status ledger、audit event templates 與收件包；它只定義 7 個 approval-required targets 的回覆請求、回覆欄位、驗收規則與拒收規則，目前 received / accepted response 皆為 0，不代表 repo creation、visibility change、refs sync 或 primary approval。 +S4.10 已補 owner decision response request packet、template status ledger、audit event templates、redaction examples 與收件包；它只定義 7 個 approval-required targets 的回覆請求、回覆欄位、驗收規則與拒收規則，目前 received / accepted response 皆為 0，不代表 repo creation、visibility change、refs sync 或 primary approval。 ## 1. 決策表 diff --git a/docs/security/SECURITY-APPROVAL-GATE.md b/docs/security/SECURITY-APPROVAL-GATE.md index b43a845a8..6d316e06b 100644 --- a/docs/security/SECURITY-APPROVAL-GATE.md +++ b/docs/security/SECURITY-APPROVAL-GATE.md @@ -38,7 +38,7 @@ S3.1 開始，實際人工決策紀錄由 `security_approval_decision_record_v1` | 1 | Redacted finding ingestion | 只批准設計或 draft PR | | 2 | Safe web crawl | 只批准低噪音 scope 定義 | | 3 | Gitea owner attestation + read-only inventory | 先依 S4.9 驗收 S4.7 owner response，再只批准只讀 inventory 或 redacted admin export | -| 4 | GitHub target decisions | 只批准逐 repo S4.10 request packet / template status ledger / audit event templates / response 與 S4.12 workflow / secret 名稱 response 驗收與決策草案 | +| 4 | GitHub target decisions | 只批准逐 repo S4.10 request packet / template status ledger / audit event templates / redaction examples / response 與 S4.12 workflow / secret 名稱 response 驗收與決策草案 | | 5 | Ref truth review | 只批准 S4.11 owner response 驗收、人工分類與 reconcile 草案 | | 6 | Credentialed scan | 只允許人工 exception 設計，仍需 runtime gate | | 7 | Kali full-upgrade / reboot | 只允許維護窗口與 rollback 規劃 | diff --git a/docs/security/SECURITY-APPROVAL-QUEUE.md b/docs/security/SECURITY-APPROVAL-QUEUE.md index 23dfc42e2..c396ef7f6 100644 --- a/docs/security/SECURITY-APPROVAL-QUEUE.md +++ b/docs/security/SECURITY-APPROVAL-QUEUE.md @@ -35,7 +35,7 @@ S3.0 開始，人工批准範圍由 `security_approval_gate_v1` 承接。S3.1 | 1 | `kali-finding-runtime-ingestion-approval-20260513` | 先接 redacted finding evidence，風險低、價值高 | | 2 | `kali-safe-web-crawl-approval-20260513` | TLS/header/basic crawl 屬低噪音，但仍需批准 scope | | 3 | `gitea-private-internal-server-side-inventory-2026-05-12` | 先依 S4.9 收到並驗收 S4.7 owner coverage attestation response，再審 Gitea 全量版本轉 GitHub 的只讀 inventory gate | -| 4 | `source-control-target-repo-approval-bundle-20260513` | 先依 S4.10 request packet / template status ledger / audit event templates 驗收逐 repo owner / visibility / canonical response，並依 S4.12 驗收 workflow / secret 名稱 owner response | +| 4 | `source-control-target-repo-approval-bundle-20260513` | 先依 S4.10 request packet / template status ledger / audit event templates / redaction examples 驗收逐 repo owner / visibility / canonical response，並依 S4.12 驗收 workflow / secret 名稱 owner response | | 5 | `source-control-ref-truth-review-bundle-20260513` | 先依 S4.11 驗收 refs truth owner response，再看 deprecated / release tag review | | 6 | `kali-credentialed-scan-approval-20260513` | 需要憑證，風險較高 | | 7 | `kali-full-upgrade-reboot-approval-20260513` | 需要維護窗口、snapshot、rollback 與 post-check | diff --git a/docs/security/SECURITY-APPROVAL-REVIEW-PACKET.md b/docs/security/SECURITY-APPROVAL-REVIEW-PACKET.md index bb6c71727..8d010ea13 100644 --- a/docs/security/SECURITY-APPROVAL-REVIEW-PACKET.md +++ b/docs/security/SECURITY-APPROVAL-REVIEW-PACKET.md @@ -39,7 +39,7 @@ S3.4 開始，等待 runtime gate 時要看哪些前置條件，由 `security_fo | 1 | Redacted finding ingestion | `design_or_draft_review` | 只審是否可設計或建立 draft PR | | 2 | Safe web crawl | `low_noise_scan_scope_review` | 只審低噪音 scope 定義 | | 3 | Gitea owner attestation + read-only inventory | `read_only_inventory_review` | 先依 S4.9 審 S4.7 owner response，再審只讀 token 或 redacted export | -| 4 | GitHub target decisions | `design_or_draft_review` | 先審 S4.10 owner response request packet / template status ledger / audit event templates / response 與 S4.12 workflow / secret 名稱 response，再審 owner / visibility / canonical 草案 | +| 4 | GitHub target decisions | `design_or_draft_review` | 先審 S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / response 與 S4.12 workflow / secret 名稱 response，再審 owner / visibility / canonical 草案 | | 5 | Ref truth review | `design_or_draft_review` | 先審 S4.11 owner response 驗收，再審人工分類與 reconcile 草案 | | 6 | Credentialed scan | `manual_exception_review` | 只審 exception 設計 | | 7 | Kali full-upgrade / reboot | `manual_exception_review` | 只審維護窗口與 rollback 計畫 | diff --git a/docs/security/SECURITY-FOLLOWUP-RUNTIME-GATE.md b/docs/security/SECURITY-FOLLOWUP-RUNTIME-GATE.md index d2d9cf233..b79bb9553 100644 --- a/docs/security/SECURITY-FOLLOWUP-RUNTIME-GATE.md +++ b/docs/security/SECURITY-FOLLOWUP-RUNTIME-GATE.md @@ -34,7 +34,7 @@ | Redacted finding ingestion | MEDIUM | 只準備 ingestion adapter 的 redaction / audit 前置條件 | | Safe web crawl scope | MEDIUM | 只準備 TLS/header/basic crawl 的低噪音 scope | | Gitea owner attestation + read-only inventory | MEDIUM | 先依 S4.9 驗收 S4.7 owner response，再準備 read-only token 或 redacted export inventory | -| GitHub target decision | HIGH | 只準備 S4.10 owner response request packet / template status ledger / audit event templates / response、S4.12 workflow / secret 名稱 response 驗收、owner / visibility / canonical / workflow parity 決策 | +| GitHub target decision | HIGH | 只準備 S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / response、S4.12 workflow / secret 名稱 response 驗收、owner / visibility / canonical / workflow parity 決策 | | Ref truth review | HIGH | 只準備 S4.11 owner response 驗收、refs truth / deprecated / release tag 人工判定 | | Credentialed scan exception | HIGH | 只準備人工 exception、credential lifecycle 與停用方式 | | Kali full-upgrade / reboot | HIGH | 只準備維護窗口、snapshot、rollback 與 post-health | diff --git a/docs/security/SECURITY-MIRROR-DRY-RUN.md b/docs/security/SECURITY-MIRROR-DRY-RUN.md index eb6228743..da5400ad7 100644 --- a/docs/security/SECURITY-MIRROR-DRY-RUN.md +++ b/docs/security/SECURITY-MIRROR-DRY-RUN.md @@ -24,7 +24,7 @@ | `CHECK_ROUTE_COVERAGE` | 確認 route groups 覆蓋所有 contracts | 不建立 fallback execution route | | `CHECK_ACCEPTANCE_AND_QUARANTINE` | 確認驗收與隔離只處理 mirror payload | 不阻擋 runtime | | `CHECK_PROGRESS_GUARD` | 確認 58% 進度估算只作狀態顯示 | 不把進度當 approval 或 runtime authorization | -| `CHECK_OWNER_RESPONSE_GUARD` | 確認四包 owner response 仍未收到 / 接受，且 S4.9 request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / preflight / outcome lanes 只提示 owner、逐項顯示 waiting、只定義 0 emitted 的 metadata audit 模板、脫敏範例與只讀 UI 區塊、維持收件狀態分離、分類可審、補證、隔離、拒收或等待；S4.10 request packet / template status ledger / audit event templates 也只提示 7 個 GitHub target 要回覆的欄位、逐項顯示 waiting / request ready、定義 0 emitted 的脫敏 metadata | 不把 guard pass、request packet、template status ledger、audit event templates 或 response packet 當成 repo、refs、workflow、secret、runner、primary、audit production ingestion 或 runtime 授權 | +| `CHECK_OWNER_RESPONSE_GUARD` | 確認四包 owner response 仍未收到 / 接受，且 S4.9 request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / preflight / outcome lanes 只提示 owner、逐項顯示 waiting、只定義 0 emitted 的 metadata audit 模板、脫敏範例與只讀 UI 區塊、維持收件狀態分離、分類可審、補證、隔離、拒收或等待；S4.10 request packet / template status ledger / audit event templates / redaction examples 也只提示 7 個 GitHub target 要回覆的欄位、逐項顯示 waiting / request ready、定義 0 emitted 的脫敏 metadata | 不把 guard pass、request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo、refs、workflow、secret、runner、primary、audit production ingestion 或 runtime 授權 | | `CHECK_LOW_NOISE_CHANNEL` | 確認 Channel Event 低噪音 | 不對 LOW / MEDIUM 洗版 | | `CONFIRM_NO_RUNTIME_ACTION` | 確認 dry-run 沒有任何 runtime action | 不掃描、不 deploy、不 sync refs | diff --git a/docs/security/SECURITY-MIRROR-READINESS.md b/docs/security/SECURITY-MIRROR-READINESS.md index 520fb0a67..0e4077020 100644 --- a/docs/security/SECURITY-MIRROR-READINESS.md +++ b/docs/security/SECURITY-MIRROR-READINESS.md @@ -87,7 +87,7 @@ AwoooP 可以將 ready / partial contracts mirror 到： 19. 再 mirror `kali_integration_status_v1` 與 `kali_scan_scope_approval_v1`。 20. 最後再 mirror source-control 其他 contracts。 -GitHub target 決策面需同時 mirror S4.10 `GITHUB-TARGET-OWNER-DECISION-RESPONSE.md` 與 `github-target-owner-decision-response.snapshot.json`，只顯示 1 個 owner response request packet、7 個 owner response template statuses、3 個 owner response audit event templates、7 個 owner decision response templates、received / accepted response 皆為 0、8 個 acceptance checks 與 10 個 rejection rules；不得把 request packet、template status ledger、audit event templates 或 response packet 當成 repo creation、visibility change、refs sync 或 GitHub primary approval。 +GitHub target 決策面需同時 mirror S4.10 `GITHUB-TARGET-OWNER-DECISION-RESPONSE.md` 與 `github-target-owner-decision-response.snapshot.json`，只顯示 1 個 owner response request packet、7 個 owner response template statuses、3 個 owner response audit event templates、5 個 owner response redaction examples、7 個 owner decision response templates、received / accepted response 皆為 0、8 個 acceptance checks 與 10 個 rejection rules；不得把 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo creation、visibility change、refs sync 或 GitHub primary approval。 Ref truth 決策面需同時 mirror S4.11 `SOURCE-CONTROL-REF-TRUTH-OWNER-RESPONSE.md` 與 `source-control-ref-truth-owner-response.snapshot.json`，只顯示 5 個 owner response templates、received / accepted response 皆為 0、8 個 acceptance checks 與 10 個 rejection rules；不得把 response packet 當成 refs sync、delete、force push 或 GitHub primary approval。 diff --git a/docs/security/SECURITY-MIRROR-STATUS-ROLLUP.md b/docs/security/SECURITY-MIRROR-STATUS-ROLLUP.md index c27a358c3..253599df9 100644 --- a/docs/security/SECURITY-MIRROR-STATUS-ROLLUP.md +++ b/docs/security/SECURITY-MIRROR-STATUS-ROLLUP.md @@ -28,7 +28,7 @@ | Review packets | S3.2 已建立；8 packets、7 ready for human review、1 block candidate | | State transitions | S3.3 已建立；5 個 decision options 都有 next state，且都不授權執行 | | Follow-up runtime gate templates | S3.4 已建立；8 個 templates、0 個 active runtime gates | -| GitHub primary readiness gate | S4.0 已建立；8 個 candidate repos、7 個 in-scope blocked、0 個 primary ready；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates 與收件包，7 個 response templates、owner response 0 筆；S4.11 已補 refs truth owner response 收件包，5 個 response templates、owner response 0 筆；S4.12 已補 workflow / secret 名稱 owner response 收件包，5 個 response templates、owner response 0 筆；S4.13 已補四包 owner response validation rollup，22 個 templates、received / accepted / rejected 皆為 0 | +| GitHub primary readiness gate | S4.0 已建立；8 個 candidate repos、7 個 in-scope blocked、0 個 primary ready；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples 與收件包，7 個 response templates、owner response 0 筆；S4.11 已補 refs truth owner response 收件包，5 個 response templates、owner response 0 筆；S4.12 已補 workflow / secret 名稱 owner response 收件包，5 個 response templates、owner response 0 筆；S4.13 已補四包 owner response validation rollup，22 個 templates、received / accepted / rejected 皆為 0 | | GitHub primary rollback ADR | S4.4 已建立；7 個 in-scope rollback drafts、0 個 owner approved、0 個 dry-run completed、0 個 active cutover | | Gitea inventory | S4.5 已補認證清冊匯出請求；S4.6 已補匯入驗收契約；S4.7 已補 owner coverage attestation；S4.8 已把既有 Gitea queue/gate/review packet/follow-up gate 對齊 attestation 先行；S4.9 已補 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、owner response 收件包、6 個 intake preflight checks 與 5 個 outcome lanes；目前 status=`partial_waiting_authenticated_inventory`、未認證公開範圍 repos 2 個、本機可見 Gitea unique repos 4 個、匯出來源選項 2 類、匯入驗收 payload 0 筆、owner attestation items 5 個、收到 attestation 0 筆、owner response 0 筆、audit events emitted 0 筆、敏感 payload 必須隔離、允許收集 token value=false | | Workflow / secret name inventory | S4.1 已建立；S4.2 補 4 個 repos、31 個 workflow files、43 個 referenced secret names 的 local evidence；S4.3 補 7 個 repos、5 類 lanes 的 redacted export request；S4.12 補 5 個 owner response templates；0 個 inventory complete、禁止收集 secret value、禁止 write token | @@ -77,7 +77,7 @@ python3 scripts/security/security-mirror-progress-guard.py 1. redacted finding ingestion adapter。 2. safe web crawl scope。 3. Gitea private/internal read-only inventory：先依 S4.9 收到並驗收 S4.7 owner coverage attestation response，且 S4.8 已把這個先行條件接到既有 approval queue / gate / review packet / follow-up runtime gate；再依 S4.5 認證匯出請求補全量清冊；收到脫敏 payload 後先依 S4.6 驗收 / 拒收 / 隔離；目前未認證公開範圍 2 個、本機可見 Gitea unique 4 個、覆蓋缺口 2 個、attestation items 5 個、owner response 0 筆，不保存 token value。 -4. GitHub target / owner / visibility / canonical：先依 S4.10 request packet、template status ledger 與 audit event templates 收到並驗收 7 個 owner decision response templates；received / accepted response 目前皆為 0，不得把 request packet、template status ledger、audit event templates 或 response packet 當成 repo creation、visibility change、refs sync 或 primary approval。 +4. GitHub target / owner / visibility / canonical：先依 S4.10 request packet、template status ledger、audit event templates 與 redaction examples 收到並驗收 7 個 owner decision response templates；received / accepted response 目前皆為 0，不得把 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo creation、visibility change、refs sync 或 primary approval。 5. Kali `/execute` 維持 block candidate。 6. Refs truth owner response：先依 S4.11 顯示 main/dev truth、deprecated drift、release tag、GitHub-only refs 的 5 個 response templates；received / accepted response 目前皆為 0，不得把 response packet 當成 refs sync、delete、force push 或 primary approval。 7. Workflow / secret 名稱 owner response：先依 S4.12 顯示 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 5 個 response templates；received / accepted response 目前皆為 0，不得把 response packet 當成 secret value 收集、workflow 修改、GitHub hosted runner 啟用或 primary approval。 diff --git a/docs/security/SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md b/docs/security/SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md index a74af50b4..76d2514f8 100644 --- a/docs/security/SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md +++ b/docs/security/SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md @@ -42,7 +42,7 @@ | `gitea_repo_inventory_v1` | mirror-only | Gitea repo 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、owner response 收件包、intake preflight checks 與 outcome lanes | public-only / blocked endpoint / S4.5 export request / S4.6 import acceptance / S4.7 coverage attestation / S4.9 response snapshots | | `local_git_remote_inventory_v1` | mirror-only | 本機 remote coverage | `local-git-remote-inventory.snapshot.json` | | `github_target_probe_v1` | mirror-only | GitHub target visibility | `github-target-probe.snapshot.json` | -| `github_target_decision_v1` | mirror-only | GitHub target 決策；S4.10 已補 owner response request packet、template status ledger、audit event templates 與 owner decision response 收件包 | `github-target-decision.snapshot.json` / `github-target-owner-decision-response.snapshot.json` | +| `github_target_decision_v1` | mirror-only | GitHub target 決策；S4.10 已補 owner response request packet、template status ledger、audit event templates、redaction examples 與 owner decision response 收件包 | `github-target-decision.snapshot.json` / `github-target-owner-decision-response.snapshot.json` | | `github_target_repo_approval_package_v1` | approval-only | 逐 repo approval queue draft；S4.10 response 通過前不得視為 repo / visibility / refs 批准 | `github-target-repo-approval-package.snapshot.json` / `github-target-owner-decision-response.snapshot.json` | | `source_control_approval_board_v1` | approval-only | 逐 repo owner / visibility / canonical / refs 決策 board | `source-control-approval-board.snapshot.json` | | `source_control_reconcile_plan_v1` | approval-only | refs-blocked repo 的 draft reconcile plan；S4.11 response 通過前只更新草案 wording | `source-control-reconcile-plan.snapshot.json` / `source-control-ref-truth-owner-response.snapshot.json` | @@ -62,7 +62,7 @@ 3. 將 snapshot mirror 成 Runtime State / Channel Event / Audit evidence。 4. 讀到 `source-control-ref-truth-owner-response.snapshot.json` 時，只顯示 S4.11 response templates、acceptance checks 與 rejection rules；不得新增 refs action。 5. 讀到 `source-control-owner-response-validation-rollup.snapshot.json` 時，只顯示 S4.9/S4.10/S4.11/S4.12 四個 response packets 的總覽：22 個 templates、received / accepted / rejected 皆為 0、cross-packet checks 10 個；不得把 rollup 當成 approval 或 execution authorization。 -6. 只對 `approval_required_event_v1`、repo approval package、`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` 建 approval candidate / review lane / next-state display / runtime gate preparation / primary readiness display / rollback ADR display / workflow-secret name inventory gate / redacted export request display；`github_target_decision_v1` 只能顯示 S4.10 owner response request packet、template status ledger、audit event templates、owner decision response templates、received_response_count=0、acceptance checks 與 rejection rules，不得觸發 repo creation、visibility change、refs sync 或 primary switch；`gitea_repo_inventory_v1` 只能顯示 S4.5 認證匯出請求、S4.6 匯入驗收契約、S4.7 owner coverage attestation request、S4.9 owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、owner response 收件包、intake preflight checks、outcome lanes 與覆蓋缺口，不得觸發 token collection 或 Gitea write。 +6. 只對 `approval_required_event_v1`、repo approval package、`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` 建 approval candidate / review lane / next-state display / runtime gate preparation / primary readiness display / rollback ADR display / workflow-secret name inventory gate / redacted export request display；`github_target_decision_v1` 只能顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、owner decision response templates、received_response_count=0、acceptance checks 與 rejection rules，不得觸發 repo creation、visibility change、refs sync 或 primary switch；`gitea_repo_inventory_v1` 只能顯示 S4.5 認證匯出請求、S4.6 匯入驗收契約、S4.7 owner coverage attestation request、S4.9 owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、owner response 收件包、intake preflight checks、outcome lanes 與覆蓋缺口，不得觸發 token collection 或 Gitea write。 7. 不新增執行按鈕，不做 runtime enforcement。 ## 3. 永久禁止 diff --git a/docs/security/SECURITY-SUPPLY-CHAIN-PROGRESS.md b/docs/security/SECURITY-SUPPLY-CHAIN-PROGRESS.md index e89b2b26b..46b83d9bf 100644 --- a/docs/security/SECURITY-SUPPLY-CHAIN-PROGRESS.md +++ b/docs/security/SECURITY-SUPPLY-CHAIN-PROGRESS.md @@ -30,7 +30,7 @@ python3 scripts/security/security-mirror-progress-guard.py | 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 與收件包 | owner / visibility / canonical response | +| 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 與收件包 | 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 | @@ -66,7 +66,7 @@ python3 scripts/security/security-mirror-progress-guard.py | 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、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 與模板回覆 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.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、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 與模板回覆 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 / 人讀版；5 個 response templates、8 個 acceptance checks、10 個 rejection rules、total ref review items 141、received response 0、accepted 0、execution authorized=false | owner 依模板回覆 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 | @@ -182,12 +182,12 @@ python3 scripts/security/security-mirror-progress-guard.py ## 3. 下一階段建議 1. 先依 S4.9 `GITEA-INVENTORY-OWNER-ATTESTATION-RESPONSE.md` 收到並驗收 S4.7 `GITEA-INVENTORY-COVERAGE-ATTESTATION.md` 的 owner response；S4.8 已把這件事接到既有 approval queue / gate / review packet / follow-up runtime gate。之後再依 S4.5 `GITEA-AUTHENTICATED-INVENTORY-EXPORT-REQUEST.md` 取得 Gitea 認證清冊；收到 payload 後依 S4.6 `GITEA-AUTHENTICATED-INVENTORY-IMPORT-ACCEPTANCE.md` 驗收 / 拒收 / 隔離。目前未認證公開範圍 2 個、本機可見 Gitea unique 4 個、覆蓋缺口 2 個、attestation items 5 個、owner response 0 筆；只能用只讀 token API 或已脫敏管理匯出補私有 / 內部 server-side 全量 repo list，不保存 token value。 -2. 依 S4.10 `GITHUB-TARGET-OWNER-DECISION-RESPONSE.md` request packet / template status ledger / audit event templates 與 `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。 +2. 依 S4.10 `GITHUB-TARGET-OWNER-DECISION-RESPONSE.md` request packet / template status ledger / audit event templates、redaction examples 與 `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。 3. 依 S4.11 `SOURCE-CONTROL-REF-TRUTH-OWNER-RESPONSE.md` 與 `SOURCE-CONTROL-REF-TRUTH-CLASSIFICATION.md` 對 `awoooi`、`clawbot-v5`、`wooo-aiops` 做單 repo / 單 ref owner response 驗收；response 通過也只更新 read-only classification / reconcile / readiness wording，仍不得 push/delete refs 或 force push。 4. 依 S4.12 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md` 與 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md` 對 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 做 owner response 驗收；response 通過也只更新 read-only inventory / export request / readiness wording，仍不得收 secret value、改 workflow 或啟用 runner。 5. 依 S4.13 `SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md` 集中檢查 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets；rollup 通過也只更新 read-only wording，不代表 approval 或 execution authorization。 6. 對 `ewoooc` / `momo-pro-system` 完成 server-side canonical 判定。 7. 依 `KALI-SCAN-SCOPE-APPROVAL-PACKAGE.md` 取得 safe crawl、credentialed scan、runtime ingestion、full-upgrade / reboot 等 gate 的人工批准；不得直接接 `/execute`。 -8. 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.13 `source_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 入口，不新增執行按鈕；其中 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 與 owner decision response templates，refs truth 需同時顯示 S4.11 owner response templates，workflow / secret inventory 需同時顯示 S4.3 redacted export request 與 S4.12 owner response templates，primary readiness 需同時顯示 S4.4 rollback ADR 草案。 +8. 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.13 `source_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 入口，不新增執行按鈕；其中 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 與 owner decision response templates，refs truth 需同時顯示 S4.11 owner response templates，workflow / secret inventory 需同時顯示 S4.3 redacted export request 與 S4.12 owner response templates，primary readiness 需同時顯示 S4.4 rollback ADR 草案。 9. AwoooP 主線消費 `security_rollout_policy_v1` 時，只做 read-only policy，不做 runtime blocking。 -10. 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 templates、S4.11 refs truth owner response templates、S4.12 workflow / secret 名稱 owner response templates、S4.13 owner response validation rollup、GitHub primary readiness blockers、rollback ADR 草案、workflow / secret 名稱 inventory 缺口、redacted export request 與 blocked reason，不新增 execution router。 +10. 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 templates、S4.11 refs truth owner response templates、S4.12 workflow / secret 名稱 owner response templates、S4.13 owner response validation rollup、GitHub primary readiness blockers、rollback ADR 草案、workflow / secret 名稱 inventory 缺口、redacted export request 與 blocked reason，不新增 execution router。 diff --git a/docs/security/SOURCE-CONTROL-APPROVAL-BOARD.md b/docs/security/SOURCE-CONTROL-APPROVAL-BOARD.md index 38f038c37..af1af5733 100644 --- a/docs/security/SOURCE-CONTROL-APPROVAL-BOARD.md +++ b/docs/security/SOURCE-CONTROL-APPROVAL-BOARD.md @@ -15,7 +15,7 @@ 本 board 只整理決策，不授權執行。AwoooP 可以 mirror 成 approval candidate，但不得建立 repo、修改 visibility、同步 refs、切 GitHub primary 或保存 credential value。 -S4.10 已補 1 個 GitHub target owner response request packet、7 個 template statuses、3 個 audit event templates 與 7 個 owner decision response templates；目前 received / accepted response 皆為 0。response 通過後也只更新本 board、decision table、approval package 與 readiness gate 的 read-only 欄位，不代表 repo creation、visibility change、refs sync 或 primary approval。 +S4.10 已補 1 個 GitHub target owner response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples 與 7 個 owner decision response templates；目前 received / accepted response 皆為 0。response 通過後也只更新本 board、decision table、approval package 與 readiness gate 的 read-only 欄位，不代表 repo creation、visibility change、refs sync 或 primary approval。 ## 1. 逐 repo 決策隊列 diff --git a/docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md b/docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md index 38d136550..2d53ec346 100644 --- a/docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md +++ b/docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md @@ -65,7 +65,7 @@ S4.13 不新增第 36 個主 contract，不新增 approval item，不啟用 runt | Lane | 缺口 | 下一步 | 仍禁止 | |------|------|--------|--------| | S4.9 Gitea owner attestation | 5 個 response templates 尚未收到 | Owner 回覆 5 個 Gitea coverage attestation items，只引用脫敏 evidence refs | 不收 token value、不寫 Gitea、不 sync refs、不切 primary | -| S4.10 GitHub target decision | 7 個 response templates 尚未收到 | Owner 依 S4.10 request packet、template status ledger 與 audit event templates 回覆 7 個 GitHub target 的 owner / visibility / canonical disposition | 不建 repo、不改 visibility、不 sync refs、不切 primary | +| S4.10 GitHub target decision | 7 個 response templates 尚未收到 | Owner 依 S4.10 request packet、template status ledger、audit event templates 與 redaction examples 回覆 7 個 GitHub target 的 owner / visibility / canonical disposition | 不建 repo、不改 visibility、不 sync refs、不切 primary | | S4.11 refs truth | 5 個 response templates 尚未收到 | Owner 回覆 refs truth、deprecated drift、release tags 與 GitHub-only refs disposition | 不 fetch / push / delete refs、不 force push、不切 primary | | S4.12 workflow / secret name | 5 個 response templates 尚未收到 | Owner 回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、secret name parity 的脫敏狀態 | 不收 secret value、不改 workflow、不啟用 runner、不切 primary | diff --git a/docs/security/SOURCE-CONTROL-PRIMARY-READINESS-GATE.md b/docs/security/SOURCE-CONTROL-PRIMARY-READINESS-GATE.md index e5af60f37..73887e3a9 100644 --- a/docs/security/SOURCE-CONTROL-PRIMARY-READINESS-GATE.md +++ b/docs/security/SOURCE-CONTROL-PRIMARY-READINESS-GATE.md @@ -40,7 +40,7 @@ | Gitea authenticated inventory | blocked | private/internal 全量 repo list 尚未完成；S4.9 owner response request packet、template status ledger、audit event templates、redaction examples、display sections 與 collection checks 已可顯示，但 S4.7 owner coverage attestation response 仍未收到，audit events emitted 仍為 0；S4.13 已集中顯示四包 owner response validation，但 total accepted response 仍為 0 | | refs truth / branch-tag parity | blocked | 3 個 mapped repos 仍有 refs drift；S4.11 已補 refs truth owner response 收件包，received / accepted response 皆為 0 | | workflow / runner / secret name parity | missing evidence | S4.1 已建立 inventory 契約；S4.12 已補 owner response 收件包，received / accepted response 皆為 0；尚未有實際 redacted workflow、webhook、runner、secret 名稱 snapshot | -| owner / visibility / canonical | pending review | 7 個 in-scope targets 仍需人工決策；S4.10 已補 owner response request packet、template status ledger、audit event templates 與收件包，received / accepted response 皆為 0 | +| owner / visibility / canonical | pending review | 7 個 in-scope targets 仍需人工決策；S4.10 已補 owner response request packet、template status ledger、audit event templates、redaction examples 與收件包，received / accepted response 皆為 0 | | rollback ADR | pending review | S4.4 已建立 rollback ADR 草案；7 個 in-scope repos 仍需 owner approval、dry-run 與 validation window | ## 3. AwoooP 可做 @@ -48,8 +48,8 @@ 1. 顯示每個 repo 的 readiness state、blockers 與 evidence refs。 2. 顯示 `primary_ready_count=0`。 3. 將 7 個 in-scope repos 維持在 approval / review lane。 -4. 顯示哪些 evidence 仍缺：Gitea authenticated inventory、S4.7 owner coverage attestation、S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / owner response、S4.10 GitHub target owner response request packet / template status ledger / audit event templates / owner response、S4.11 refs truth owner response、S4.12 workflow / secret name owner response、S4.13 validation rollup、workflow/runner/secret name inventory、rollback ADR。 -5. 連到 S4.10 `github_target_owner_decision_response_v1` 顯示 1 個 owner response request packet、7 個 owner response template statuses、3 個 owner response audit event templates、7 個 owner decision response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0。 +4. 顯示哪些 evidence 仍缺：Gitea authenticated inventory、S4.7 owner coverage attestation、S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / owner response、S4.10 GitHub target owner response request packet / template status ledger / audit event templates / redaction examples / owner response、S4.11 refs truth owner response、S4.12 workflow / secret name owner response、S4.13 validation rollup、workflow/runner/secret name inventory、rollback ADR。 +5. 連到 S4.10 `github_target_owner_decision_response_v1` 顯示 1 個 owner response request packet、7 個 owner response template statuses、3 個 owner response audit event templates、5 個 owner response redaction examples、7 個 owner decision response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0。 6. 連到 S4.11 `source_control_ref_truth_owner_response_v1` 顯示 5 個 refs owner response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0。 7. 連到 `source_control_workflow_secret_name_inventory_v1` 顯示 8 個 candidate repos 的 inventory lane 缺口與 S4.2 local evidence；只保存 secret 名稱與 owner，不保存 value。 8. 連到 S4.12 `source_control_workflow_secret_name_owner_response_v1` 顯示 5 個 owner response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0。 @@ -71,6 +71,6 @@ S4.0 只是把「切換前一定要看見什麼」先定義清楚。 -S4.4 已補上 rollback ADR 草案，但它只是 owner review 的資料包，不是切換批准。S4.7 已補上 Gitea coverage owner attestation，S4.9 已補上 Gitea owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、收件包、preflight 與 outcome lanes，S4.10 已補上 GitHub target owner decision response request packet、template status ledger、audit event templates 與收件包，S4.11 已補上 refs truth owner response 收件包，S4.12 已補上 workflow / secret 名稱 owner response 收件包，S4.13 已補上四包 owner response validation rollup；它們只是 scope decision、response 收件提示、metadata audit template、脫敏範例、只讀顯示順序與驗收框架，不是 audit production ingestion、migration approval、repo creation approval、visibility change approval、refs sync approval、delete approval、force-push approval、secret value collection approval、workflow modification approval 或 primary approval。`owner_approved_count=0`、`dry_run_completed_count=0`、`active_cutover_count=0`。 +S4.4 已補上 rollback ADR 草案，但它只是 owner review 的資料包，不是切換批准。S4.7 已補上 Gitea coverage owner attestation，S4.9 已補上 Gitea owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、收件包、preflight 與 outcome lanes，S4.10 已補上 GitHub target owner decision response request packet、template status ledger、audit event templates、redaction examples 與收件包，S4.11 已補上 refs truth owner response 收件包，S4.12 已補上 workflow / secret 名稱 owner response 收件包，S4.13 已補上四包 owner response validation rollup；它們只是 scope decision、response 收件提示、metadata audit template、脫敏範例、只讀顯示順序與驗收框架，不是 audit production ingestion、migration approval、repo creation approval、visibility change approval、refs sync approval、delete approval、force-push approval、secret value collection approval、workflow modification approval 或 primary approval。`owner_approved_count=0`、`dry_run_completed_count=0`、`active_cutover_count=0`。 這讓長期回到 GitHub 的方向可以繼續往前，但仍維持低摩擦：目前只 mirror、只顯示、只留痕，不執行。 diff --git a/docs/security/github-target-owner-decision-response.snapshot.json b/docs/security/github-target-owner-decision-response.snapshot.json index 92a606d46..041f22890 100644 --- a/docs/security/github-target-owner-decision-response.snapshot.json +++ b/docs/security/github-target-owner-decision-response.snapshot.json @@ -23,6 +23,7 @@ "owner_response_request_packet_count": 1, "owner_response_template_status_count": 7, "owner_response_audit_event_template_count": 3, + "owner_response_redaction_example_count": 5, "response_template_count": 7, "received_response_count": 0, "accepted_response_count": 0, @@ -416,6 +417,158 @@ "not_approval": true } ], + "owner_response_redaction_examples": [ + { + "example_id": "redaction-github-target-doc-ref", + "display_order": 1, + "example_status": "template_example_only", + "category": "github_target_existing_document_reference", + "safe_response_shape": [ + "template_id=target-awoooi-refs-blocked", + "decision=hold_pending_refs_truth", + "canonical_source=wooo/awoooi", + "evidence_refs=[docs/security/GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md, docs/security/source-control-ref-detail-diff.snapshot.json]", + "decision_reason=引用既有 snapshot 與決策表，不貼 API raw body 或 repo archive" + ], + "required_redactions": [ + "外部 evidence 只保留 repo 內文件路徑、snapshot 路徑或已脫敏 metadata pointer", + "GitHub API 查詢結果只能摘要為 repo slug、status、review owner 與 evidence ref", + "不得貼完整 API request/response body、header 或 private clone URL" + ], + "forbidden_raw_values": [ + "token_value", + "secret_value", + "private_clone_url_credential", + "api_request_header", + "api_response_raw_body", + "repo_archive" + ], + "stored_raw_payload_allowed": false, + "awooop_display_mode": "display_redaction_example_only", + "execution_authorized": false, + "not_approval": true + }, + { + "example_id": "redaction-owner-visibility-canonical-metadata", + "display_order": 2, + "example_status": "template_example_only", + "category": "owner_visibility_canonical_metadata", + "safe_response_shape": [ + "owner_role_or_team=repo-owner-or-platform-team", + "visibility_review_owner=security-commander", + "canonical_source=unknown_requires_more_evidence", + "decision=unknown_requires_more_evidence", + "followup_owner=source-control-owner" + ], + "required_redactions": [ + "只寫角色或團隊，不寫個人密碼、session、one-time code 或 API token", + "visibility decision reason 不得包含可重播的管理操作步驟或憑證", + "followup_owner 只代表責任 owner，不代表 repo creation、visibility change 或 primary approval" + ], + "forbidden_raw_values": [ + "password", + "cookie", + "session", + "one_time_code", + "approval_phrase_as_execution_authorization", + "admin_console_screenshot_with_secret" + ], + "stored_raw_payload_allowed": false, + "awooop_display_mode": "display_redaction_example_only", + "execution_authorized": false, + "not_approval": true + }, + { + "example_id": "redaction-private-target-access-metadata", + "display_order": 3, + "example_status": "template_example_only", + "category": "private_or_new_target_metadata", + "safe_response_shape": [ + "template_id=target-ewoooc-private-or-new", + "github_repo=owenhytsai/ewoooc", + "decision=approve_private_target_access_request", + "github_target_disposition=private_access_request_only", + "credential_value_stored=false" + ], + "required_redactions": [ + "private target 只能寫 repo slug、access request status 與 owner metadata", + "完整 clone URL 只能保留 host、namespace、repo slug；若含 userinfo、query token 或 header 必須移除值", + "不得把 private access request 當成可建立 repo、可 fetch、可 push 或可改 visibility 的指令" + ], + "forbidden_raw_values": [ + "https_userinfo_credential", + "query_token", + "authorization_header", + "ssh_private_key", + "deploy_key_value", + "git_remote_with_secret" + ], + "stored_raw_payload_allowed": false, + "awooop_display_mode": "display_redaction_example_only", + "execution_authorized": false, + "not_approval": true + }, + { + "example_id": "redaction-refs-truth-dependency-summary", + "display_order": 4, + "example_status": "template_example_only", + "category": "refs_truth_dependency_summary", + "safe_response_shape": [ + "template_id=target-clawbot-v5-refs-blocked", + "decision=hold_pending_refs_truth", + "refs_truth_review_owner=source-control-owner", + "server_side_refs_diff_owner=platform-ops", + "blocked_until=[S4.11 refs truth owner response, S4.12 workflow secret name owner response]" + ], + "required_redactions": [ + "只保留 refs truth 責任 owner、blocking contract 與 evidence ref", + "若引用外部 diff，必須先轉成 repo 內 snapshot 或 redacted metadata pointer", + "不得貼 git object pack、repo archive、可執行 sync/delete/force-push 指令或 unrelated history merge request" + ], + "forbidden_raw_values": [ + "git_object_pack", + "repo_archive", + "refs_sync_command", + "delete_refs_command", + "force_push_command", + "unrelated_history_merge_request" + ], + "stored_raw_payload_allowed": false, + "awooop_display_mode": "display_redaction_example_only", + "execution_authorized": false, + "not_approval": true + }, + { + "example_id": "redaction-github-target-quarantine-pointer", + "display_order": 5, + "example_status": "template_example_only", + "category": "uncertain_sensitive_payload", + "safe_response_shape": [ + "collection_status=quarantine_sensitive_payload", + "quarantine_reason=疑似含 GitHub token、private URL credential、repo archive 或未脫敏截圖", + "raw_payload_stored_in_repo=false", + "next_owner_action=request_redacted_metadata_pointer" + ], + "required_redactions": [ + "不確定是否含敏感值時先產生 quarantine pointer", + "只留下原因、來源類型、責任 owner 與下一步，不留下原文", + "解除 quarantine 前不得更新 received / accepted count 或 target decision wording" + ], + "forbidden_raw_values": [ + "owner_response_raw_body", + "github_token_or_pat", + "secret_screenshot", + "private_clone_url_credential", + "credential_file", + "repo_archive", + "execution_request_payload" + ], + "stored_raw_payload_allowed": false, + "awooop_display_mode": "display_redaction_example_only", + "execution_authorized": false, + "not_approval": true + } + ], "response_templates": [ { "template_id": "target-awoooi-refs-blocked", diff --git a/docs/security/security-approval-gate.snapshot.json b/docs/security/security-approval-gate.snapshot.json index 51a6a3d41..2961f1c5d 100644 --- a/docs/security/security-approval-gate.snapshot.json +++ b/docs/security/security-approval-gate.snapshot.json @@ -139,7 +139,7 @@ ], "decision_options": ["approve_scope", "reject", "defer", "request_more_evidence"], "allowed_after_approval": [ - "依 S4.10 request packet / template status ledger / audit event templates 驗收 owner decision response", + "依 S4.10 request packet / template status ledger / audit event templates / redaction examples 驗收 owner decision response", "依 S4.12 驗收 workflow / secret 名稱 owner response", "逐 repo 更新 owner/visibility/canonical decision", "更新 workflow / secret name parity read-only wording", @@ -149,7 +149,7 @@ "still_forbidden": [ "建立 repo", "修改 visibility", - "把 S4.10 request packet、template status ledger、audit event templates 或 response packet 當成 repo creation 或 visibility approval", + "把 S4.10 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo creation 或 visibility approval", "把 S4.12 response packet 當成 secret value collection、workflow modification 或 runner enablement approval", "push refs", "delete refs", diff --git a/docs/security/security-approval-queue.snapshot.json b/docs/security/security-approval-queue.snapshot.json index d4db1bf72..4e91119a5 100644 --- a/docs/security/security-approval-queue.snapshot.json +++ b/docs/security/security-approval-queue.snapshot.json @@ -126,7 +126,7 @@ "risk": "HIGH", "state": "pending_approval", "recommended_awooop_mode": "approve_required", - "requested_decision": "是否依 S4.10 request packet / template status ledger / audit event templates 逐 repo 收到並驗收 GitHub target、owner、visibility、canonical response，並依 S4.12 驗收 workflow / secret 名稱 owner response；此 bundle 不授權執行。", + "requested_decision": "是否依 S4.10 request packet / template status ledger / audit event templates / redaction examples 逐 repo 收到並驗收 GitHub target、owner、visibility、canonical response，並依 S4.12 驗收 workflow / secret 名稱 owner response；此 bundle 不授權執行。", "blocked_until_approved": true, "required_reviewers": [ "migration-engineer", @@ -143,7 +143,7 @@ "docs/security/source-control-workflow-secret-name-owner-response.snapshot.json" ], "allowed_after_approval": [ - "依 S4.10 request packet / template status ledger / audit event templates 驗收 owner decision response", + "依 S4.10 request packet / template status ledger / audit event templates / redaction examples 驗收 owner decision response", "依 S4.12 驗收 workflow / secret 名稱 owner response", "逐 repo 更新 owner/visibility/canonical decision", "更新 workflow / secret name parity read-only wording", @@ -153,7 +153,7 @@ "still_forbidden": [ "建立 repo", "修改 visibility", - "把 S4.10 request packet、template status ledger、audit event templates 或 response packet 當成 repo creation 或 visibility approval", + "把 S4.10 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo creation 或 visibility approval", "把 S4.12 response packet 當成 secret value collection、workflow modification 或 runner enablement approval", "push refs", "delete refs", diff --git a/docs/security/security-approval-review-packet.snapshot.json b/docs/security/security-approval-review-packet.snapshot.json index 8eb176e26..ed1749082 100644 --- a/docs/security/security-approval-review-packet.snapshot.json +++ b/docs/security/security-approval-review-packet.snapshot.json @@ -175,7 +175,7 @@ ], "allowed_pre_decision_actions": [ "顯示 7 個 approval-required target", - "顯示 S4.10 owner response request packet、template status ledger、audit event templates、owner response templates、received_response_count=0 與 rejection rules", + "顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、owner response templates、received_response_count=0 與 rejection rules", "顯示 S4.12 workflow / secret 名稱 owner response templates、received_response_count=0 與 rejection rules", "要求 repo owner 補 owner/visibility/canonical 判定", "維持 refs action disabled" @@ -187,7 +187,7 @@ "still_forbidden": [ "建立 repo", "修改 visibility", - "把 S4.10 request packet、template status ledger、audit event templates 或 response packet 當成 repo creation 或 visibility approval", + "把 S4.10 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo creation 或 visibility approval", "把 S4.12 response packet 當成 secret value collection、workflow modification 或 runner enablement approval", "push refs", "delete refs", diff --git a/docs/security/security-followup-runtime-gate.snapshot.json b/docs/security/security-followup-runtime-gate.snapshot.json index 47bb01942..9d263edf8 100644 --- a/docs/security/security-followup-runtime-gate.snapshot.json +++ b/docs/security/security-followup-runtime-gate.snapshot.json @@ -157,7 +157,7 @@ "gate_state": "waiting_approved_scope", "applies_after_decision": "approve_scope", "minimum_required_evidence": [ - "S4.10 owner response request packet / template status ledger / audit event templates / decision response 驗收結果：docs/security/github-target-owner-decision-response.snapshot.json", + "S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / decision response 驗收結果：docs/security/github-target-owner-decision-response.snapshot.json", "S4.12 workflow / secret 名稱 owner response 驗收結果：docs/security/source-control-workflow-secret-name-owner-response.snapshot.json", "repo owner / visibility / canonical decision", "GitHub target 是否已存在的最新 probe", @@ -170,7 +170,7 @@ "human-owner" ], "preflight_checks": [ - "確認 S4.10 request packet、template status ledger、audit event templates 或 response packet 未被當成 repo creation、visibility change、refs sync 或 primary approval", + "確認 S4.10 request packet、template status ledger、audit event templates、redaction examples 或 response packet 未被當成 repo creation、visibility change、refs sync 或 primary approval", "確認 S4.12 response packet 未被當成 secret value collection、workflow modification、runner enablement 或 primary approval", "確認 not_found_or_private 不被當成可自動建立 repo", "確認 visibility change 仍未授權", diff --git a/docs/security/security-mirror-dry-run.snapshot.json b/docs/security/security-mirror-dry-run.snapshot.json index 9b708a72f..ca62a92f7 100644 --- a/docs/security/security-mirror-dry-run.snapshot.json +++ b/docs/security/security-mirror-dry-run.snapshot.json @@ -107,7 +107,7 @@ }, { "step_id": "CHECK_OWNER_RESPONSE_GUARD", - "expected_observation": "AwoooP dry-run 必須確認 S4.9 / S4.10 / S4.11 / S4.12 四包 owner response 仍為 waiting_owner_response，received / accepted 皆為 0，且 S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / intake preflight / outcome lanes 只提示 owner，S4.10 owner response request packet 只提示 7 個 GitHub target 要回覆的 owner / visibility / canonical 欄位，S4.10 template status ledger 逐項顯示 waiting / request ready，S4.10 audit event templates 只定義 0 emitted 的脫敏 metadata，並維持 request / received / accepted 分離；不能把 request shown、response received metadata 或 outcome classified 當成 approval，不能解鎖 repo、refs、workflow、secret、runner、GitHub primary、audit production ingestion 或 runtime action。", + "expected_observation": "AwoooP dry-run 必須確認 S4.9 / S4.10 / S4.11 / S4.12 四包 owner response 仍為 waiting_owner_response，received / accepted 皆為 0，且 S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / intake preflight / outcome lanes 只提示 owner，S4.10 owner response request packet 只提示 7 個 GitHub target 要回覆的 owner / visibility / canonical 欄位，S4.10 template status ledger 逐項顯示 waiting / request ready，S4.10 audit event templates 只定義 0 emitted 的脫敏 metadata，S4.10 redaction examples 只顯示可接受的脫敏 metadata shape，並維持 request / received / accepted 分離；不能把 request shown、response received metadata 或 outcome classified 當成 approval，不能解鎖 repo、refs、workflow、secret、runner、GitHub primary、audit production ingestion 或 runtime action。", "evidence_refs": [ "docs/security/source-control-owner-response-validation-rollup.snapshot.json", "docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md", diff --git a/docs/security/security-mirror-readiness.snapshot.json b/docs/security/security-mirror-readiness.snapshot.json index 5b90099ef..9ed0cbf23 100644 --- a/docs/security/security-mirror-readiness.snapshot.json +++ b/docs/security/security-mirror-readiness.snapshot.json @@ -287,7 +287,7 @@ "docs/security/GITHUB-TARGET-VISIBILITY-DECISION-TABLE.md", "docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md" ], - "notes": "可 mirror target decision、S4.10 owner response request packet、template status ledger、audit event templates 與 owner response templates；repo 建立、visibility 修改、refs sync 與 primary switch 仍需後續人工批准與 runtime gate。" + "notes": "可 mirror target decision、S4.10 owner response request packet、template status ledger、audit event templates、redaction examples 與 owner response templates；repo 建立、visibility 修改、refs sync 與 primary switch 仍需後續人工批准與 runtime gate。" }, { "contract": "github_target_repo_approval_package_v1", @@ -303,7 +303,7 @@ "docs/security/GITHUB-TARGET-REPO-APPROVAL-PACKAGE.md", "docs/security/GITHUB-TARGET-OWNER-DECISION-RESPONSE.md" ], - "notes": "可 mirror 逐 repo approval package、S4.10 owner response request packet、template status ledger、audit event templates 與 owner decision response 收件包；不得執行 item。" + "notes": "可 mirror 逐 repo approval package、S4.10 owner response request packet、template status ledger、audit event templates、redaction examples 與 owner decision response 收件包；不得執行 item。" }, { "contract": "source_control_approval_board_v1", diff --git a/docs/security/security-mirror-status-rollup.snapshot.json b/docs/security/security-mirror-status-rollup.snapshot.json index 3d16a09a1..21f986535 100644 --- a/docs/security/security-mirror-status-rollup.snapshot.json +++ b/docs/security/security-mirror-status-rollup.snapshot.json @@ -143,8 +143,8 @@ { "phase_id": "S4_migration_execution", "state": "not_started", - "current_result": "GitHub primary 是長期方向；source_control_primary_readiness_gate_v1 已定義 8 個 candidate repos、7 個 in-scope blocked repos、0 個 primary ready；S4.1 已定義 workflow / secret 名稱 inventory 契約；S4.2 已補 local evidence；S4.3 已補 redacted export request；S4.4 已補 rollback ADR 草案；S4.5 已補 Gitea authenticated inventory export request；S4.6 已補 redacted import acceptance；S4.7 已補 owner coverage attestation request；S4.9 已補 Gitea owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、owner response intake packet、6 個 intake preflight checks 與 5 個 outcome lanes；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates 與 intake packet；S4.11 已補 refs truth owner response intake packet；S4.12 已補 workflow / secret 名稱 owner response intake packet；S4.13 已補四包 owner response validation rollup，彙整 22 個 templates、received=0、accepted=0，並標示 next_collection_candidate=S4.9，但 inventory status 仍 partial，S4.9 audit events emitted 仍 0 筆，GitHub target / refs truth / workflow-secret response 仍 0 筆。", - "next_gate": "依 S4.13 先集中檢查四包 owner response validation 狀態，AwoooP 只顯示 next_collection_candidate=S4.9 Gitea owner attestation，依 S4.9 owner response request packet 要求 owner 回覆，並用 template status ledger / audit event templates / redaction examples / display sections / collection checks 維持 request / received / accepted 分離；再依 S4.9 收到並驗收 S4.7 Gitea owner response、依 S4.10 request packet、template status ledger 與 audit event templates 收到並驗收 7 個 GitHub target owner / visibility / canonical response、依 S4.11 收到並驗收 5 個 refs truth owner response templates、依 S4.12 收到並驗收 5 個 workflow / secret 名稱 owner response templates、authenticated inventory payload 通過 S4.6 驗收、rollback ADR owner approval 與逐 repo 人工批准。" + "current_result": "GitHub primary 是長期方向；source_control_primary_readiness_gate_v1 已定義 8 個 candidate repos、7 個 in-scope blocked repos、0 個 primary ready；S4.1 已定義 workflow / secret 名稱 inventory 契約；S4.2 已補 local evidence；S4.3 已補 redacted export request；S4.4 已補 rollback ADR 草案；S4.5 已補 Gitea authenticated inventory export request；S4.6 已補 redacted import acceptance；S4.7 已補 owner coverage attestation request；S4.9 已補 Gitea owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、owner response intake packet、6 個 intake preflight checks 與 5 個 outcome lanes；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples 與 intake packet；S4.11 已補 refs truth owner response intake packet；S4.12 已補 workflow / secret 名稱 owner response intake packet；S4.13 已補四包 owner response validation rollup，彙整 22 個 templates、received=0、accepted=0，並標示 next_collection_candidate=S4.9，但 inventory status 仍 partial，S4.9 audit events emitted 仍 0 筆，GitHub target / refs truth / workflow-secret response 仍 0 筆。", + "next_gate": "依 S4.13 先集中檢查四包 owner response validation 狀態，AwoooP 只顯示 next_collection_candidate=S4.9 Gitea owner attestation，依 S4.9 owner response request packet 要求 owner 回覆，並用 template status ledger / audit event templates / redaction examples / display sections / collection checks 維持 request / received / accepted 分離；再依 S4.9 收到並驗收 S4.7 Gitea owner response、依 S4.10 request packet、template status ledger、audit event templates 與 redaction examples 收到並驗收 7 個 GitHub target owner / visibility / canonical response、依 S4.11 收到並驗收 5 個 refs truth owner response templates、依 S4.12 收到並驗收 5 個 workflow / secret 名稱 owner response templates、authenticated inventory payload 通過 S4.6 驗收、rollback ADR owner approval 與逐 repo 人工批准。" } ], "next_safe_actions": [ @@ -277,13 +277,13 @@ "mode": "approval_required", "source_contract": "source_control_approval_board_v1", "allowed_processing": [ - "顯示 S4.10 owner response request packet、template status ledger、audit event templates、owner decision response templates、received_response_count=0 與 rejection rules", + "顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、owner decision response templates、received_response_count=0 與 rejection rules", "逐 repo 更新 owner / visibility / canonical decision", "產生 draft reconcile plan 或 ADR", "維持 refs action disabled" ], "blocked_processing": [ - "把 S4.10 request packet、template status ledger、audit event templates 或 response packet 當成 repo creation、visibility change、refs sync 或 primary approval", + "把 S4.10 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當成 repo creation、visibility change、refs sync 或 primary approval", "建立 repo", "修改 visibility", "push / delete refs", @@ -398,7 +398,7 @@ "S4.7 只新增 Gitea owner coverage attestation request；required_attestation_item_count=5、received_attestation_count=0，不把 attestation 當 migration approval。", "S4.8 只把既有 Gitea approval queue/gate/review packet/follow-up gate 對齊 S4.7 先行條件；approval_queue_total 仍為 8、active_runtime_gates 仍為 0，不新增執行入口。", "S4.9 只新增 Gitea owner attestation response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks 與 response 收件包；owner_response_request_packet_count=1、owner_response_template_status_count=5、owner_response_audit_event_template_count=3、owner_response_redaction_example_count=5、owner_response_display_section_count=8、owner_response_collection_check_count=6、required_response_item_count=5、received_response_count=0、accepted_response_count=0、audit_events_emitted=0，不把 request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks 或 response packet 當 inventory 執行、audit production ingestion 或 primary approval。", - "S4.10 新增 GitHub target owner decision response request packet、template status ledger、audit event templates 與收件包；owner_response_request_packet_count=1、owner_response_template_status_count=7、owner_response_audit_event_template_count=3、response_template_count=7、received_response_count=0、accepted_response_count=0，不把 request packet、template status ledger、audit event templates 或 response packet 當 repo creation、visibility change、refs sync 或 GitHub primary approval。", + "S4.10 新增 GitHub target owner decision response request packet、template status ledger、audit event templates、redaction examples 與收件包；owner_response_request_packet_count=1、owner_response_template_status_count=7、owner_response_audit_event_template_count=3、owner_response_redaction_example_count=5、response_template_count=7、received_response_count=0、accepted_response_count=0，不把 request packet、template status ledger、audit event templates、redaction examples 或 response packet 當 repo creation、visibility change、refs sync 或 GitHub primary approval。", "S4.11 只新增 refs truth owner response 收件包；response_template_count=5、received_response_count=0、accepted_response_count=0，不把 response packet 當 refs sync、delete、force push 或 GitHub primary approval。", "S4.12 只新增 workflow / secret 名稱 owner response 收件包；response_template_count=5、received_response_count=0、accepted_response_count=0，不把 response packet 當 secret value collection、workflow modification、GitHub hosted runner enablement 或 GitHub primary approval。", "S4.13 只新增 owner response validation rollup；response_packet_count=4、template_count=22、received_response_count=0、accepted_response_count=0、cross_packet_check_count=10、next_collection_candidate=S4.9，不把 rollup 當 approval、runtime gate 或 execution authorization。" diff --git a/docs/security/security-supply-chain-contract-manifest.snapshot.json b/docs/security/security-supply-chain-contract-manifest.snapshot.json index 5d4cc0c27..8e5ba1620 100644 --- a/docs/security/security-supply-chain-contract-manifest.snapshot.json +++ b/docs/security/security-supply-chain-contract-manifest.snapshot.json @@ -450,7 +450,7 @@ "consumption_mode": "mirror_only", "allowed_actions": ["mirror_target_decision", "create_approval_candidate"], "forbidden_actions": ["change_visibility", "create_repo", "sync_refs"], - "notes": "8 個 targets 中 7 個需要人工批准；S4.10 已補 owner response request packet、template status ledger、audit event templates 與 owner decision response 收件包，owner_response_request_packet_count=1、owner_response_template_status_count=7、owner_response_audit_event_template_count=3、received_response_count=0，不授權 repo / visibility / refs / primary 動作。" + "notes": "8 個 targets 中 7 個需要人工批准；S4.10 已補 owner response request packet、template status ledger、audit event templates、redaction examples 與 owner decision response 收件包，owner_response_request_packet_count=1、owner_response_template_status_count=7、owner_response_audit_event_template_count=3、owner_response_redaction_example_count=5、received_response_count=0，不授權 repo / visibility / refs / primary 動作。" }, { "contract": "github_target_repo_approval_package_v1", @@ -467,7 +467,7 @@ "consumption_mode": "approval_only", "allowed_actions": ["display_repo_approval_queue", "request_owner_decision"], "forbidden_actions": ["execute_approval_item", "push_refs", "change_visibility"], - "notes": "7 個 pending packages，逐 repo 低摩擦批准；S4.10 只定義 owner response request packet、template status ledger、audit event templates 與驗收 / 拒收格式，不代表任何執行批准。" + "notes": "7 個 pending packages，逐 repo 低摩擦批准；S4.10 只定義 owner response request packet、template status ledger、audit event templates、redaction examples 與驗收 / 拒收格式，不代表任何執行批准。" }, { "contract": "source_control_approval_board_v1", diff --git a/docs/security/source-control-approval-board.snapshot.json b/docs/security/source-control-approval-board.snapshot.json index 36f8f82c7..78c3cbfc5 100644 --- a/docs/security/source-control-approval-board.snapshot.json +++ b/docs/security/source-control-approval-board.snapshot.json @@ -9,7 +9,7 @@ "allowed_next_step": [ "提供 read-only token 後重跑 gitea-repo-inventory", "或提供 redacted admin export JSON", - "依 S4.10 request packet / template status ledger / audit event templates 收到 GitHub target owner / visibility / canonical response 後更新 read-only board 欄位", + "依 S4.10 request packet / template status ledger / audit event templates / redaction examples 收到 GitHub target owner / visibility / canonical response 後更新 read-only board 欄位", "在 gate 前仍可維護 approval board 與 decision table" ], "still_forbidden": [ diff --git a/docs/security/source-control-owner-response-validation-rollup.snapshot.json b/docs/security/source-control-owner-response-validation-rollup.snapshot.json index 7e1458264..9b048dc2f 100644 --- a/docs/security/source-control-owner-response-validation-rollup.snapshot.json +++ b/docs/security/source-control-owner-response-validation-rollup.snapshot.json @@ -333,7 +333,7 @@ "received_response_count": 0, "accepted_response_count": 0, "current_status": "waiting_owner_response", - "next_owner_action": "Owner 需依 S4.10 request packet、template status ledger 與 audit event templates 回覆 7 個 GitHub target 的 owner / visibility / canonical disposition。", + "next_owner_action": "Owner 需依 S4.10 request packet、template status ledger、audit event templates 與 redaction examples 回覆 7 個 GitHub target 的 owner / visibility / canonical disposition。", "awooop_display_mode": "observe_missing_response", "still_forbidden": [ "create_github_repo", diff --git a/docs/security/source-control-primary-readiness-gate.snapshot.json b/docs/security/source-control-primary-readiness-gate.snapshot.json index 53650c1e5..87d863d9a 100644 --- a/docs/security/source-control-primary-readiness-gate.snapshot.json +++ b/docs/security/source-control-primary-readiness-gate.snapshot.json @@ -126,13 +126,13 @@ ], "current_gap": [ "7 個 targets 仍需人工批准", - "S4.10 已建立 GitHub target owner decision response request packet、template status ledger、audit event templates 與收件包，但目前 received_response_count=0、accepted_response_count=0", + "S4.10 已建立 GitHub target owner decision response request packet、template status ledger、audit event templates、redaction examples 與收件包，但目前 received_response_count=0、accepted_response_count=0", "ewoooc / momo-pro-system canonical 關係尚未確認", "bitan-pharmacy 與 tsenyang-website GitHub target 未確認" ], "allowed_now": [ "顯示 approval board", - "mirror S4.10 owner response request packet、template status ledger、audit event templates、owner decision response templates、acceptance checks 與 rejection rules", + "mirror S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、owner decision response templates、acceptance checks 與 rejection rules", "要求 repo owner 補決策", "更新 visibility decision table" ], diff --git a/scripts/security/source-control-owner-response-guard.py b/scripts/security/source-control-owner-response-guard.py index b653de15e..aa5c92ec2 100755 --- a/scripts/security/source-control-owner-response-guard.py +++ b/scripts/security/source-control-owner-response-guard.py @@ -123,6 +123,13 @@ LANES = [ "audit-github-target-response-received-metadata", "audit-github-target-response-outcome-classified", ], + "expected_redaction_examples": [ + "redaction-github-target-doc-ref", + "redaction-owner-visibility-canonical-metadata", + "redaction-private-target-access-metadata", + "redaction-refs-truth-dependency-summary", + "redaction-github-target-quarantine-pointer", + ], }, { "lane_id": "s4_11_ref_truth_owner_response",