wooo/awoooi
1
1
Fork 0
Code Issues 2 Pull Requests 1 Actions 2 Packages Projects Releases Wiki Activity

feat(web): surface iwooos progress and compact ux

Browse Source
This commit is contained in:
Your Name
2026-05-26 00:31:48 +08:00
parent 480292b04d
commit eba2bd4fd0
13 changed files with 1667 additions and 1352 deletions
Download Patch File Download Diff File Expand all files Collapse all files

218
apps/web/messages/en.json
View File

@@ -1267,7 +1267,7 @@
"title": "已納入 IwoooS 只讀資安鏡像",
"subtitle": "這個既有安全 / 合規頁面現在會反向標示 IwoooS 納管狀態；只顯示整體進度、框架成熟度與 runtime 邊界，不新增掃描、修復、批准或部署按鈕。",
"compactTitle": "IwoooS",
"compactDetail": "58% / gate 0",
"compactDetail": "61% / gate 0",
"openIwooos": "開啟 IwoooS",
"sourceLabel": "整合來源",
"sourceDetail": "SecurityPanel、CompliancePanel、standalone /security 與 /compliance 仍保留原本資料來源；IwoooS 只做資安網索引與 mirror-only 姿態彙整。",
@@ -2099,48 +2099,48 @@
"item4": "Open the AwoooP work map"
},
"securityMirror": {
"title": "IwoooS Security Mirror",
"subtitle": "AwoooP home displays IwoooS / security mirror state as a read-only candidate so operators can understand security mesh progress and boundaries. This is not production_landing_enabled and does not connect an execution router.",
"badge": "Read-only candidate",
"openIwooos": "Open IwoooS",
"checkpointsTitle": "Intake Checks",
"boundaryLabel": "Safety Boundary",
"boundaryTitle": "Still in the low-friction framework phase",
"boundaryDetail": "This panel displays committed snapshot and guard semantics only. It does not call Kali, GitHub, Gitea, or runtime APIs, and it does not provide scan, execute, repair, deploy, primary switch, or refs actions.",
"title": "IwoooS 資安鏡像",
"subtitle": "AwoooP 首頁已以正式只讀方式顯示 IwoooS / 資安鏡像狀態，讓使用者理解資安網進度與邊界；這不是執行入口，也不接執行路由器。",
"badge": "正式只讀",
"openIwooos": "開啟 IwoooS",
"checkpointsTitle": "接入檢查",
"boundaryLabel": "安全邊界",
"boundaryTitle": "仍維持低摩擦框架期",
"boundaryDetail": "這個面板只顯示已提交快照與防護檢查口徑，不呼叫 Kali、GitHub、Gitea 或執行期 API，也不提供掃描、執行、修復、部署、主要來源切換或分支 / 標籤參照動作。",
"metrics": {
"headline": {
"label": "Overall Security Mesh",
"detail": "The headline still waits for 負責人回覆, redacted ingestion, 執行期閘門, GitHub primary, or AwoooP production landing evidence."
"label": "整體資安網",
"detail": "已因 AwoooP 正式只讀 landing 證據保守重估；其餘 owner response、runtime gate 與 GitHub primary 仍等待。"
},
"framework": {
"label": "Framework Maturity",
"detail": "Governance, docs, schemas, read-only evidence, and IwoooS projection are close to complete."
"label": "框架成熟度",
"detail": "治理、文件、結構定義、只讀證據與 IwoooS 投影已接近完整。"
},
"runtime": {
"label": "Runtime Landing",
"detail": "Runtime ingestion, GitHub primary, and AwoooP production landing still require later evidence."
"label": "落地執行",
"detail": "AwoooP 只讀 landing 已有證據；執行期匯入、GitHub 主要來源與 runtime gate 仍未開。"
},
"activeGates": {
"label": "Active Runtime Gates",
"detail": "Currently 0; any host or blocking control still needs separate approval."
"label": "主動執行閘門",
"detail": "目前維持 0，任何主機或阻擋型控制都仍需獨立批准。"
}
},
"checkpoints": {
"iwooosProjection": {
"title": "IwoooS projection is readable",
"detail": "AwoooP displays only IwoooS posture, progress, evidence refs, and forbidden actions."
"title": "IwoooS 投影可讀",
"detail": "AwoooP 只顯示 IwoooS 態勢、進度、證據參照與禁止動作。"
},
"rollupGuard": {
"title": "Guard semantics match",
"detail": "Before handoff, keep security-mirror-progress-guard.py and source-control-owner-response-guard.py green."
"title": "防護檢查口徑一致",
"detail": "接手前維持 security-mirror-progress-guard.py 與 source-control-owner-response-guard.py 綠燈。"
},
"ownerResponse": {
"title": "負責人回覆 still waiting",
"detail": "S4.9 through S4.12 已收到 / 已接受 remain 0; display state is not completed validation."
"title": "負責人回覆仍等待",
"detail": "S4.9 到 S4.12 收到 / 接受都仍為 0，不把顯示狀態當驗收完成。"
},
"productionLanding": {
"title": "Production landing is not complete",
"detail": "AwoooP main line still needs deployment proof and read-only consumption evidence before headline review."
"title": "正式只讀入口已完成",
"detail": "已以正式站部署與只讀消費證據納入 61% 重估；仍不代表 execution router 或 runtime 授權。"
}
}
},
@@ -2441,8 +2441,8 @@
"remediationWrites": "Writes: incident={incident}; autoRepair={autoRepair}",
"timelineReady": "時間線 gate is not currently a top gap",
"timelineMissing": "Quality summary still reports a 時間線 / audit gap",
"iwooosSecurityMirror": "Overall {headline}; framework {framework}; landing {runtime}; active 執行期閘門s={gates}",
"iwooosSecurityMirrorOwner": "負責人回覆 is still waiting; production_landing_enabled=false",
"iwooosSecurityMirror": "整體 {headline}；框架 {framework}；落地 {runtime}；主動執行閘門={gates}",
"iwooosSecurityMirrorOwner": "AwoooP 正式只讀 landing 已驗證；負責人回覆仍等待",
"iwooosSecurityMirrorBoundary": "execution_router_linked=false; runtime_execution_authorized=false; action_buttons_allowed=false",
"githubPrimaryReadiness": "候選專案庫={candidates}；範圍內={inScope}；主要來源就緒={ready}",
"githubPrimaryOwnerResponses": "負責人回覆 remains 0/22; request-ready is not accepted",
@@ -3854,7 +3854,7 @@
"activeRuntimeGates": "主動執行期閘門",
"activeRuntimeGatesDetail": "Any 執行期閘門 still needs separate approval plus rollback and 後檢證據.",
"headline": "Overall Security Mesh",
"headlineDetail": "58% is only reviewed when 負責人回覆, 執行期閘門, GitHub primary, or production landing evidence changes."
"headlineDetail": "已因 AwoooP 正式只讀落地證據重估到 61%；下一次仍要靠負責人回覆、執行期閘門或 GitHub 主要來源證據。"
},
"checks": {
"s49OwnerAttestation": {
@@ -4640,6 +4640,32 @@
"state": "只讀鏡像 / 先觀測",
"detail": "All numbers come from verified snapshots and guards. This page only displays posture, gaps, next gates, and non-blocking lanes."
},
"informationArchitecture": {
"overview": {
"title": "一眼看懂",
"summary": "預設只展開 headline、下一個 gate、進度移動條件與目前仍鎖住的邊界。"
},
"frontStage": {
"title": "前台入口與既有資安頁",
"summary": "整合安全合規、告警、授權、治理、稽核與 Code Review 的只讀入口。"
},
"progressPath": {
"title": "下一步與阻塞解除",
"summary": "集中顯示低摩擦 rollout、非阻擋分流、第一個可讓 61% 往前的證據路徑。"
},
"ownerEvidence": {
"title": "版本來源與負責人回覆",
"summary": "保留 Gitea / GitHub owner response、S4.9 收件、預檢與人工決策證據。"
},
"awooopVersion": {
"title": "AwoooP 只讀落地與版本證據",
"summary": "收納產品 rollout、AwoooP production landing、evidence wiring 與跨 Session 交接。"
},
"hostKali": {
"title": "主機與 Kali 邊界",
"summary": "將 192.168.0.112 / 111 / 168 的 observe-only、收件與人工決策證據收在進階區。"
}
},
"metrics": {
"overall": {
"label": "Overall mesh",
@@ -4713,7 +4739,7 @@
},
"progressHolding": {
"title": "Progress display holding",
"body": "58% means high-level gates are pending; it is neither stuck nor runtime approval."
"body": "61% means high-level gates are pending; it is neither stuck nor runtime approval."
}
},
"existingSurfaces": {
@@ -4790,7 +4816,7 @@
},
"legacySecurity": {
"title": "Legacy Security Monitor",
"body": "The standalone security page now shows the IwoooS read-only bridge and 58% / gate 0 boundary.",
"body": "The standalone security page now shows the IwoooS read-only bridge and 61% / gate 0 boundary.",
"boundary": "Keeps error and security signals visible without turning the page into a scan entrypoint."
},
"legacyCompliance": {
@@ -4888,7 +4914,7 @@
"steps": {
"readPosture": {
"title": "Read Current Posture",
"body": "Start from the 58% headline, framework / runtime landing, active gates, and next high-level gate.",
"body": "Start from the 61% headline, framework / runtime landing, active gates, and next high-level gate.",
"output": "read-only posture, not authorization"
},
"openSurface": {
@@ -6410,47 +6436,47 @@
}
},
"progressHoldMovementGates": {
"title": "Why 58% Is Still Holding",
"subtitle": "S2.50 把 headline 進度的移動門檻直接顯示出來：目前不是沒有推進，而是五個會讓 58% 進入下一輪重估的閘門都還沒有實質 evidence。框架、文件、前端可見性會累積在 86-88% 框架進度，但不會灌水成落地百分比。",
"gateLabel": "Movement gate",
"moveLabel": "When it moves",
"guardLabel": "No inflation rule",
"title": "為什麼現在是 61%",
"subtitle": "AwoooP 正式只讀 landing 已有部署與消費證據，所以 headline 從 58% 保守重估到 61%。其餘四個高層 gate 仍是 0 / false，框架、文件與前端可見性不會被灌水成 runtime 執行。",
"gateLabel": "移動門檻",
"moveLabel": "什麼時候會動",
"guardLabel": "不灌水原則",
"items": {
"ownerResponseAccepted": {
"title": "負責人回覆 accepted is still 0",
"body": "S4.9-S4.12 still have no 負責人回覆 已收到 / 已接受; S4.9 is request-ready only.",
"move": "The headline can be reviewed after the first redacted 負責人回覆s pass S4.9 preflight and the S4.13 rollup.",
"guard": "Do not treat request-ready, templates, preflight, or focus as 已收到 / 已接受."
"title": "負責人回覆 accepted 仍是 0",
"body": "S4.9-S4.12 都還沒有負責人回覆 已收到 / 已接受，S4.9 目前只是 request-ready。",
"move": "第一批脫敏負責人回覆通過 S4.9 preflight 與 S4.13 rollup 後，headline 才有重估依據。",
"guard": "不把 request-ready、範本、preflight 或焦點當成 已收到 / 已接受。"
},
"redactedPayloadIngested": {
"title": "Redacted payload ingestion is not enabled",
"body": "Evidence refs, redaction examples, quarantine, and preflight exist, but there is no accepted payload ingestion yet.",
"move": "Runtime landing can be reviewed after redacted payloads are approved, pass preflight, and enter read-only ingestion.",
"guard": "No raw payloads, credential plaintext, or doc examples as ingestion."
"title": "脫敏 payload 匯入仍未啟用",
"body": "目前只定義 evidence refs、redaction examples、quarantine 與 preflight，尚未有 accepted payload ingestion。",
"move": "脫敏 payload 經人工批准、通過 preflight、進入只讀 ingestion 後，runtime landing 才能重估。",
"guard": "不收原始載荷、不收 credential plaintext、不把文件範例當 ingestion。"
},
"activeRuntimeGate": {
"title": "Active 執行期閘門 is still 0",
"body": "Kali `/execute`, SSH, host updates, blocking control, repo / refs / workflow actions remain outside an active gate.",
"move": "It moves only after human approval, scope, rollback, post-check metrics, and a separate active 執行期閘門.",
"guard": "Do not open 執行期閘門s from IwoooS, progress numbers, or checklists."
"title": "主動 執行期閘門 仍是 0",
"body": "Kali `/execute`、SSH、主機更新、blocking control、repo / refs / workflow 動作都仍在獨立 gate 之外。",
"move": "人工批准、scope、rollback、post-check metrics 完整，並另開 active 執行期閘門 後才會動。",
"guard": "不從 IwoooS 前端、progress 數字或 checklist 開 執行期閘門。"
},
"githubPrimaryReady": {
"title": "GitHub primary ready is still 0",
"body": "GitHub targets, refs truth, 工作流程 / 機密 name parity, and rollback ADR are still in owner-response / readiness phases.",
"move": "primary_ready_count can become greater than 0 after at least one repo passes target, refs, 工作流程 / 機密 name, and rollback readiness.",
"guard": "No repo creation, refs sync, primary switch, or candidate as readiness."
"title": "GitHub 主要來源就緒數仍是 0",
"body": "GitHub target、refs truth、工作流程 / 機密 name parity、rollback ADR 都還在負責人回覆 / 就緒度階段。",
"move": "至少一批 repo 通過 target、refs、工作流程 / 機密 name 與 rollback readiness，primary_ready_count 才可大於 0。",
"guard": "不建 repo、不 sync refs、不切主要來源、不把候選項當就緒。"
},
"awooopReadOnlyLanding": {
"title": "AwoooP landing is not yet production-consumed",
"body": "IwoooS is visible, but the AwoooP main line still needs read-only consumption of rollup, evidence refs, and guard results without execution routing.",
"move": "User-visible progress improves after AwoooP consumes this state read-only and passes guard checks, still without production execution.",
"guard": "Read-only landing is not an 操作按鈕, approval, runtime execution, or blocking control."
"title": "AwoooP 正式只讀 landing 已驗證",
"body": "正式站已能在 AwoooP / IwoooS / 安全頁只讀顯示資安鏡像進度、證據邊界與禁止動作，且沒有接 execution router。",
"move": "這項證據已推動 headline 從 58% 重估到 61%；後續仍要等 owner response、runtime gate 或 GitHub primary 才能再動。",
"guard": "read-only landing 不是 操作按鈕、approval、runtime execution 或 blocking control。"
}
}
},
"headlineMovementAcceptanceGate": {
"title": "58% 重估驗收閘門",
"subtitle": "S2.100 把下一次 headline 能不能從 58% 往前推的判定規則固定下來：只有真正收到並驗收脫敏負責人回覆、脫敏匯入、人工 執行期閘門、GitHub 主要來源就緒或 AwoooP production landing evidence，才會開啟重估；目前五個移動訊號仍都是 0 / false。",
"title": "61% 重估驗收紀錄",
"subtitle": "S2.100 的五個高層 gate 中，AwoooP production landing evidence 已有正式部署與只讀消費證據，因此本次只把 headline 從 58% 保守重估到 61%；其餘 owner response、脫敏匯入、執行期閘門與 GitHub 主要來源仍是 0 / false。",
"gateLabel": "重估 gate",
"acceptanceLabel": "驗收條件",
"guardLabel": "仍禁止",
@@ -6458,11 +6484,11 @@
"summary": {
"headline": {
"label": "目前 headline",
"detail": "仍維持 58%，不把框架層堆疊灌水成落地執行。"
"detail": "已從 58% 保守重估到 61%，不把框架層堆疊灌水成落地執行。"
},
"signals": {
"label": "移動訊號",
"detail": "五個高層 gate 目前全部未滿足。"
"detail": "五個高層 gate 中 1 個已有正式只讀 landing 證據。"
},
"s49Accepted": {
"label": "S4.9 accepted",
@@ -6470,13 +6496,13 @@
},
"review": {
"label": "重估紀錄",
"detail": "尚未開啟 headline review record。"
"detail": "已建立本次 headline review record；runtime 仍未授權。"
}
},
"items": {
"s49OwnerResponseAccepted": {
"title": "S4.9 負責人回覆驗收",
"body": "下一個真正會推動 58% 的 P0 是 Gitea owner attestation：public-only / local gap、org/user endpoint、110 adjacent scope、repo owner canonical scope、legacy / inaccessible disposition 五項要收到脫敏 evidence。",
"body": "下一個真正會推動 61% 的 P0 是 Gitea owner attestation：public-only / local gap、org/user endpoint、110 adjacent scope、repo owner canonical scope、legacy / inaccessible disposition 五項要收到脫敏 evidence。",
"acceptance": "五項都通過 preflight 與 S4.13 validation rollup，才可記錄 owner_response_accepted_count > 0。",
"guard": "不代填、不催收、不標記 已收到 / 已接受、不建立審批紀錄。"
},
@@ -6500,14 +6526,14 @@
},
"awooopProductionLandingProof": {
"title": "AwoooP 正式只讀消費證據",
"body": "使用者要有感，AwoooP 主線必須能只讀消費 rollup、evidence refs、guard result 與 forbidden actions。",
"acceptance": "有 PR / deployment proof 證明 production 主線只讀顯示，且沒有接 execution router，才可視為 landing evidence。",
"body": "AwoooP 主線已在正式站只讀消費 IwoooS / security mirror 的 headline、evidence refs、guard result 與 forbidden actions。",
"acceptance": "已有 Gitea main commit、CD 成功與正式站路由驗證；execution_router_linked=false、runtime_execution_authorized=false。",
"guard": "只讀 landing 不是 approval、操作按鈕、execution router 或 blocking control。"
},
"nextHeadlineReviewRecord": {
"title": "下一次 headline review record",
"body": "等任一高層 gate 真的有 evidence 後，才建立重估紀錄，說明為何從 58% 調整或為何仍維持。",
"acceptance": "review record 必須引用具體 evidence refs、guard output、風險邊界與禁止動作清單。",
"title": "本次 headline review record",
"body": "本次重估只引用 AwoooP 正式只讀 landing 證據，說明為何從 58% 調整到 61%。",
"acceptance": "review record 必須引用具體 evidence refs、guard output、風險邊界與禁止動作清單；本次仍鎖 runtime。",
"guard": "不因為新增看板、文件或清單就調整 headline。"
}
}
@@ -6684,7 +6710,7 @@
},
"ownerResponseCollectionBoard": {
"title": "下一步人工收件作戰板",
"subtitle": "把真正能推動 58% 的下一步集中顯示：S4.9-S4.12 四包負責人回覆都還是 0 已收到 / 0 已接受。本看板只讓人知道要收什麼，不會寄送、建立、接受或執行任何動作。",
"subtitle": "把真正能推動 61% 的下一步集中顯示：S4.9-S4.12 四包負責人回覆都還是 0 已收到 / 0 已接受。本看板只讓人知道要收什麼，不會寄送、建立、接受或執行任何動作。",
"packetLabel": "收件包",
"movementLabel": "收件條件",
"guardLabel": "仍不會做",
@@ -8013,14 +8039,14 @@
},
"progressAcceleration": {
"title": "Progress Acceleration And Real Unlock Points",
"subtitle": "Progress is moving, but the 58% headline only gets reassessed when 負責人回覆s, 執行期閘門s, GitHub primary readiness, or AwoooP production landing produce real evidence. This board makes the next visible unlock points explicit.",
"subtitle": "Progress is moving, but the 61% headline only gets reassessed when 負責人回覆s, 執行期閘門s, GitHub primary readiness, or AwoooP production landing produce real evidence. This board makes the next visible unlock points explicit.",
"laneLabel": "Acceleration lane",
"unlockLabel": "Unlock signal",
"guardLabel": "Low-friction boundary remains",
"items": {
"ownerResponses": {
"title": "Converge 負責人回覆s first",
"body": "S4.9-S4.12 負責人回覆s for Gitea, GitHub targets, refs truth, and 工作流程 / 機密 names are the main reason the headline is holding at 58%.",
"body": "S4.9-S4.12 負責人回覆s for Gitea, GitHub targets, refs truth, and 工作流程 / 機密 names are the main reason the headline is holding at 61%.",
"unlock": "The headline can be reassessed only after the first accepted redacted 負責人回覆s arrive.",
"guard": "Redacted evidence only; no repo creation, refs sync, workflow mutation, or 機密明文值 collection."
},
@@ -8058,7 +8084,7 @@
},
"ownerResponseNextActionFocus": {
"title": "Owner Response Next-Action Focus",
"subtitle": "S2.47 makes the owner-response work that can actually move the 58% headline explicit: collect S4.9 Gitea owner attestation first, then GitHub targets, refs truth, and 工作流程 / 機密 names. This is display-only: no chasing, autofill, or received marking.",
"subtitle": "S2.47 makes the owner-response work that can actually move the 61% headline explicit: collect S4.9 Gitea owner attestation first, then GitHub targets, refs truth, and 工作流程 / 機密 names. This is display-only: no chasing, autofill, or received marking.",
"focusLabel": "Next focus",
"nextLabel": "Evidence to inspect",
"guardLabel": "Still forbidden",
@@ -8363,14 +8389,14 @@
}
},
"progressMovementSignals": {
"title": "58% 進度移動訊號驗收條",
"subtitle": "S2.113 把真正會讓整體資安網 headline 往前的訊號拉到 IwoooS：負責人回覆、脫敏證據匯入、執行期閘門、GitHub 主要來源就緒與 AwoooP 落地證據目前都還是 0 或 false，所以進度維持 58%。",
"title": "61% 進度移動訊號驗收條",
"subtitle": "S2.113 把真正會讓整體資安網 headline 往前的訊號拉到 IwoooS：AwoooP 落地證據已驗證為 1，讓整體從 58% 保守重估到 61%；負責人回覆、脫敏證據匯入、執行期閘門與 GitHub 主要來源仍是 0 或 false。",
"boundaryTitle": "進度移動驗收邊界",
"boundaryIntro": "以下鍵值固定：這是 headline 移動條件的只讀驗收條，不是進度灌水、批准、掃描、修復、部署、主機變更或版本來源操作入口。",
"summary": {
"headline": {
"label": "目前進度",
"detail": "仍維持 58%，不把框架細節灌水。"
"detail": "已依正式只讀 landing 證據重估到 61%，不把框架細節灌水。"
},
"signals": {
"label": "移動訊號",
@@ -8378,7 +8404,7 @@
},
"passed": {
"label": "已通過",
"detail": "目前 0，還沒有 headline 移動證據。"
"detail": "目前 1，AwoooP 正式只讀 landing 是第一個 headline 移動證據。"
},
"runtime": {
"label": "執行期閘門",
@@ -8410,7 +8436,7 @@
},
"concreteSecurityWorkMap": {
"title": "目前具體工作地圖",
"subtitle": "S2.123 回應「很難理解有哪些具體工作」：把目前資安網拆成六條實體工作流。已完成的是前台可視化與只讀框架；真正會推動 58% 的下一步仍是 S4.9 負責人回覆被收到、脫敏並接受。",
"subtitle": "S2.123 回應「很難理解有哪些具體工作」：把目前資安網拆成六條實體工作流。已完成的是前台可視化與只讀框架；真正會推動 61% 的下一步仍是 S4.9 負責人回覆被收到、脫敏並接受。",
"workLabel": "工作",
"boundaryTitle": "具體工作邊界",
"boundaryIntro": "以下鍵值固定：這張圖只是把具體工作流講清楚，不是 runtime 授權、Kali 掃描、主機變更、repo/refs/workflow/secret 操作、GitHub primary 切換或 Gitea 停用。",
@@ -8425,7 +8451,7 @@
},
"realGate": {
"label": "下一真門檻",
"detail": "S4.9 負責人回覆 accepted 才會讓 58% 有機會移動。"
"detail": "S4.9 負責人回覆 accepted 才會讓 61% 有機會移動。"
},
"runtime": {
"label": "執行授權",
@@ -8436,7 +8462,7 @@
"frontstageVisibility": {
"title": "前台資安入口與使用者可視化",
"body": "已把 IwoooS、既有安全/合規頁、AwoooP 首頁/工作鏈路/審批/合約/租戶/執行監控接成只讀資安視圖。",
"evidence": "具體產出：使用者現在能從前台看見 58%、GitHub readiness、負責人回覆、host coverage 與 執行期閘門 0。"
"evidence": "具體產出：使用者現在能從前台看見 61%、GitHub readiness、負責人回覆、host coverage 與 執行期閘門 0。"
},
"hostScopeInventory": {
"title": "主機與範圍盤點框架",
@@ -8450,7 +8476,7 @@
},
"ownerEvidenceIntake": {
"title": "S4.9 負責人回覆與脫敏證據收件",
"body": "已把第一個能推動 58% 的路徑拆成工作單、封套欄位、送件前檢查、送件鏈路與第一解鎖證據包。",
"body": "已把第一個能推動 61% 的路徑拆成工作單、封套欄位、送件前檢查、送件鏈路與第一解鎖證據包。",
"evidence": "具體產出：下一步很明確，是收到並驗收可追溯的 S4.9 負責人回覆；目前 received/accepted 仍是 0。"
},
"reviewerHumanFlow": {
@@ -8533,12 +8559,12 @@
},
"concreteSecurityBlockerResolution": {
"title": "目前阻塞與解除條件",
"subtitle": "S2.125 把 58% 無法前進的原因拆成六個阻塞點。每個阻塞點都標明為什麼卡住，以及要用哪種脫敏證據或人工 gate 才能解除；這仍是只讀狀態，不是批准或執行入口。",
"subtitle": "S2.125 把 61% 無法前進的原因拆成六個阻塞點。每個阻塞點都標明為什麼卡住，以及要用哪種脫敏證據或人工 gate 才能解除；這仍是只讀狀態，不是批准或執行入口。",
"blockerLabel": "阻塞",
"whyLabel": "卡住原因",
"unlockLabel": "解除條件",
"boundaryTitle": "阻塞解除邊界",
"boundaryIntro": "以下鍵值固定：阻塞解除圖只說明為什麼 headline 仍是 58%，不會自動收件、開 reviewer queue、啟動 Kali、改主機、同步 refs、切 GitHub primary 或停用 Gitea。",
"boundaryIntro": "以下鍵值固定：阻塞解除圖只說明為什麼 headline 仍是 61%，不會自動收件、開 reviewer queue、啟動 Kali、改主機、同步 refs、切 GitHub primary 或停用 Gitea。",
"summary": {
"blockers": {
"label": "阻塞點",
@@ -8592,7 +8618,7 @@
},
"threeAxisProductProgress": {
"title": "三軸進度與全產品套用範圍",
"subtitle": "S2.126 回應「是否也套用在所有專案產品」：所有專案產品都套用同一套三軸進度，但第一階段只套只讀治理與可視化，不自動套 runtime enforcement。這讓框架進度、整體加權進度與落地執行進度分開顯示，不再只看到 58%。",
"subtitle": "S2.126 回應「是否也套用在所有專案產品」：所有專案產品都套用同一套三軸進度，但第一階段只套只讀治理與可視化，不自動套 runtime enforcement。這讓框架進度、整體加權進度與落地執行進度分開顯示，不再只看到 61%。",
"scopeLabel": "範圍",
"currentLabel": "目前套用",
"nextLabel": "下一步",
@@ -8602,7 +8628,7 @@
"summary": {
"headline": {
"label": "整體加權",
"detail": "保守維持 58%，等真證據才移動。"
"detail": "已因 AwoooP 正式只讀 landing 證據保守重估到 61%。"
},
"framework": {
"label": "框架建置",
@@ -8610,7 +8636,7 @@
},
"runtime": {
"label": "落地執行",
"detail": "仍是 35-40%，執行期閘門 仍未開。"
"detail": "提升到 40-45%，但執行期閘門仍未開。"
},
"products": {
"label": "產品套用",
@@ -9711,14 +9737,14 @@
},
"firstProgressUnlockPath": {
"title": "第一個進度解鎖路徑",
"subtitle": "S2.114 把 58% 下一個真正能往前的路徑收斂到 S4.9 負責人回覆：先收到可追溯回覆，再補齊脫敏證據參照，通過收件預檢與審查接受後，才可能成為 headline review 候選。",
"subtitle": "S2.114 把 61% 下一個真正能往前的路徑收斂到 S4.9 負責人回覆：先收到可追溯回覆，再補齊脫敏證據參照，通過收件預檢與審查接受後，才可能成為 headline review 候選。",
"stepLabel": "步驟",
"boundaryTitle": "第一解鎖路徑邊界",
"boundaryIntro": "以下鍵值固定：這是 S4.9 第一解鎖路徑的只讀收斂，不是送件完成、回覆已收到、批准、掃描、修復、部署或執行期入口。",
"summary": {
"focus": {
"label": "目前焦點",
"detail": "S4.9 是第一個可能推動 58% 的收件路徑。"
"detail": "S4.9 是第一個可能推動 61% 的收件路徑。"
},
"steps": {
"label": "解鎖步驟",
@@ -9758,7 +9784,7 @@
},
"firstUnlockEvidencePacket": {
"title": "第一解鎖證據包",
"subtitle": "S2.115 把 S4.9 要讓 58% 真正前進所需的證據收斂成五個欄位：負責人判定 metadata、範圍與來源參照、脫敏聲明、收件預檢軌跡、審查接受摘要。這裡只顯示要補什麼，不收 raw payload、不收機密明文、不開 headline review。",
"subtitle": "S2.115 把 S4.9 要讓 61% 真正前進所需的證據收斂成五個欄位：負責人判定 metadata、範圍與來源參照、脫敏聲明、收件預檢軌跡、審查接受摘要。這裡只顯示要補什麼，不收 raw payload、不收機密明文、不開 headline review。",
"slotLabel": "欄位",
"boundaryTitle": "證據包收件邊界",
"boundaryIntro": "以下鍵值固定：這是第一解鎖證據包的只讀欄位定義，不是送件、收件、驗收通過、審批、掃描、修復、部署或執行期入口。",
@@ -10158,7 +10184,7 @@
},
"s49OwnerResponseWorkOrder": {
"title": "S4.9 Owner Response 人工收件工作單",
"subtitle": "S2.101 把第一個真正能推動 58% 的 S4.9 回覆收件格式放到 IwoooS：每項都要包含 owner role/team、decision、decision reason、受影響 scope、脫敏 evidence refs 與 follow-up owner。這裡只是人工收件工作單，不送出 request、不收件、不標記 已收到 / 已接受。",
"subtitle": "S2.101 把第一個真正能推動 61% 的 S4.9 回覆收件格式放到 IwoooS：每項都要包含 owner role/team、decision、decision reason、受影響 scope、脫敏 evidence refs 與 follow-up owner。這裡只是人工收件工作單，不送出 request、不收件、不標記 已收到 / 已接受。",
"itemLabel": "收件項目",
"requiredFieldsLabel": "必填欄位",
"acceptanceLabel": "驗收方式",
@@ -10541,10 +10567,10 @@
"guard": "Do not merge, deploy, switch primary, or mutate refs from the handoff."
},
"progressSemantics": {
"title": "Progress semantics",
"body": "headline 仍是 58%，framework 86-88%，runtime / ingestion / GitHub primary / AwoooP production landing 35-40%。",
"handoff": "New UI, docs, and snapshots stay in the framework_detail ledger unless 負責人回覆, 執行期閘門, GitHub primary, or production landing evidence exists.",
"guard": "Do not treat framework detail, readiness, handoff, or guard pass as headline delta."
"title": "進度語義",
"body": "headline 仍是 61%，framework 86-88%，runtime / ingestion / GitHub primary / AwoooP production landing 40-45%。",
"handoff": "AwoooP production landing evidence 已記錄；後續新 UI / docs / snapshot 仍只能進 framework_detail ledger，除非 負責人回覆、執行期閘門或 GitHub primary 有新 evidence。",
"guard": "不把 framework detail、readiness、handoff、guard pass 當 headline delta。"
},
"requiredGuardCommands": {
"title": "Required guards",
@@ -10565,10 +10591,10 @@
"guard": "Do not store raw payloads, credential plaintext, token values, or execution payloads."
},
"nextCoordinationGate": {
"title": "Next coordination gate",
"body": "The next high-level gates that can move the headline remain 負責人回覆 accepted, redacted payload ingestion, active 執行期閘門, GitHub primary ready, or AwoooP production landing.",
"handoff": "If the other Session advances production landing, it must provide read-only consumption evidence and deployment proof.",
"guard": "Do not treat handoff packets as production consumption."
"title": "下一個協調 Gate",
"body": "AwoooP production landing 已成為第一個完成的高層 gate；下一個真正能再推動 headline 的 gate 是負責人回覆 accepted、redacted payload ingestion、active 執行期閘門或 GitHub primary ready。",
"handoff": "另一個 Session 若要繼續推進，必須沿用這份 read-only consumption evidence，不得把它升級成 execution router。",
"guard": "不把 handoff packet 或 landing evidence 當 runtime execution。"
}
}
}