109 lines
27 KiB
JSON
109 lines
27 KiB
JSON
{
|
||
"schema_version": "sre_ai_agent_conversation_commitments_v1",
|
||
"program_id": "AIA-SRE-P0-20260715",
|
||
"generated_at": "2026-07-22T17:50:52+08:00",
|
||
"source_scope": "This Codex AI Agent task only; cross-task delegation envelopes are excluded.",
|
||
"authoritative_for_execution_order": false,
|
||
"raw_conversation_embedded": false,
|
||
"secret_values_recorded": false,
|
||
"priority_contract": "Each commitment inherits priority and execution order from linked AIA-SRE parent work items; this registry does not reorder current_p0 or immediate_execution_queue.",
|
||
"status_legend": {
|
||
"analysis_or_governance_complete": "Analysis or working-method evidence exists; this is not product runtime closure.",
|
||
"source_implemented_runtime_pending": "Source evidence exists but production runtime and recipient-visible closure are not verified.",
|
||
"in_progress": "Active obligation without complete terminal evidence.",
|
||
"not_started_or_no_current_evidence": "No implementation or current verification evidence is recorded in this task.",
|
||
"superseded": "A later direct user instruction replaced this obligation."
|
||
},
|
||
"commitments": [
|
||
{"id":"AIA-CONV-001","category":"fixed_architecture","status":"in_progress","title":"落實 Alert 到 Incident Closure 與 KM/RAG/MCP/PlayBook 的固定 AI Agent 全鏈路","linked_work_items":["AIA-SRE-001","AIA-SRE-015"],"terminal_condition":"同一 run 的 canonical identity、調查、政策、受控執行、獨立驗證、通知與學習 receipt 全部可讀回。"},
|
||
{"id":"AIA-CONV-002","category":"fixed_architecture","status":"in_progress","title":"K3s workload 固定使用 Kubernetes executor/verifier","linked_work_items":["AIA-SRE-007"],"terminal_condition":"allowlisted K3s canary 由唯一 Kubernetes executor 執行並由獨立 rollout verifier 關閉。"},
|
||
{"id":"AIA-CONV-003","category":"fixed_architecture","status":"in_progress","title":"Host/systemd 固定使用 Host Ansible executor","linked_work_items":["AIA-SRE-008"],"terminal_condition":"主機服務操作只走 typed Ansible inventory，並留下 rollback 與 post-verifier receipt。"},
|
||
{"id":"AIA-CONV-004","category":"fixed_architecture","status":"in_progress","title":"Docker Compose/Sentry 使用所在主機專屬 container PlayBook","linked_work_items":["AIA-SRE-005"],"terminal_condition":"exact-container 候選只能由 identity-bound PlayBook 處置並通過容器健康驗證。"},
|
||
{"id":"AIA-CONV-005","category":"fixed_architecture","status":"source_implemented_runtime_pending","title":"Windows/VMware 固定交給 Host99 Agent99","linked_work_items":["AIA-SRE-006","AIA-SRE-009"],"terminal_condition":"production 同 run dispatch、callback、verifier、Telegram 與 learning receipt 完整。"},
|
||
{"id":"AIA-CONV-006","category":"fixed_architecture","status":"in_progress","title":"DB 使用專屬 verifier 與 bounded executor","linked_work_items":["AIA-SRE-010"],"terminal_condition":"DB check/apply/second-pod verify 受 session/headroom gate 約束並留下 same-trace receipt。"},
|
||
{"id":"AIA-CONV-007","category":"fixed_architecture","status":"in_progress","title":"Backup/restore 維持只讀調查與 critical break-glass","linked_work_items":["AIA-SRE-011"],"terminal_condition":"預設只讀 readback；任何 backup/restore/delete/retention 寫入均維持 break-glass。"},
|
||
{"id":"AIA-CONV-008","category":"fixed_architecture","status":"in_progress","title":"Unknown asset 建 drift work item 並禁止 fallback AUTO","linked_work_items":["AIA-SRE-003"],"terminal_condition":"未知資產 terminal 為 asset_identity_unresolved，runtime write 與 fallback 均為零。"},
|
||
{"id":"AIA-CONV-009","category":"fixed_architecture","status":"in_progress","title":"Circuit-open 禁止滑落到其他主機或 domain","linked_work_items":["AIA-SRE-004"],"terminal_condition":"circuit-open 留在原 domain，建立 repair work item 並證明零跨域 dispatch。"},
|
||
{"id":"AIA-CONV-010","category":"fixed_architecture","status":"in_progress","title":"告警不得只停在建議下一步","linked_work_items":["AIA-SRE-015"],"terminal_condition":"每個告警必須 apply/verify/closure，或以具體安全原因進入 fail-closed terminal。"},
|
||
|
||
{"id":"AIA-CONV-011","category":"ai_provider","status":"in_progress","title":"Provider 順序固定為 GCP-A、GCP-B、Host111 Ollama、Claude API、Gemini API","linked_work_items":["AIA-SRE-013"],"terminal_condition":"source、runtime route 與告警 attribution 均顯示相同五路順序且不得跨序滑落。"},
|
||
{"id":"AIA-CONV-012","category":"ai_provider","status":"source_implemented_runtime_pending","title":"Claude API 安全上線並做 SRE/K3s/架構任務實測","linked_work_items":["AIA-SRE-013"],"terminal_condition":"protected-secret generation、sanitized canary、latency/token/cost 與 finalized receipt 可驗證。"},
|
||
{"id":"AIA-CONV-013","category":"ai_provider","status":"source_implemented_runtime_pending","title":"Gemini API 解鎖、安全上線並驗證更新後 credential","linked_work_items":["AIA-SRE-013"],"terminal_condition":"受保護 secret reference 完成 generation 驗證，raw credential 不進 repo、API、log 或告警。"},
|
||
{"id":"AIA-CONV-014","category":"ai_provider","status":"in_progress","title":"定義 Ollama、Claude、Gemini 的 RCA、critic、開發與 domain 分工","linked_work_items":["AIA-SRE-012","AIA-SRE-013"],"terminal_condition":"同一 fixture 的 provider role、輸出 schema、policy 消費與 fallback terminal 都可重播。"},
|
||
{"id":"AIA-CONV-015","category":"ai_provider","status":"source_implemented_runtime_pending","title":"用同批 production 告警比較 Ollama、Claude、Gemini 的準確度、延遲、成本與修復成功率","linked_work_items":["AIA-SRE-013","AIA-SRE-016"],"terminal_condition":"sanitized replay 產生可比較 scorecard，且不以 shadow 結果冒充 production repair。"},
|
||
{"id":"AIA-CONV-016","category":"ai_provider","status":"analysis_or_governance_complete","title":"依 24 小時 808 alerts、538 repair triggers 評估 6-12M tokens/day 容量","linked_work_items":["AIA-SRE-016"],"terminal_condition":"容量估算已交付；後續以 production usage receipt 校正。"},
|
||
{"id":"AIA-CONV-017","category":"ai_provider","status":"analysis_or_governance_complete","title":"評估 Ollama Cloud 方案與本地/GCP/Cloud 成本差異","linked_work_items":["AIA-SRE-013","AIA-SRE-016"],"terminal_condition":"方案評估已交付；任何付費切換仍須 cost gate 與 runtime receipt。"},
|
||
{"id":"AIA-CONV-018","category":"ai_provider","status":"source_implemented_runtime_pending","title":"Gemini 最終付費備援加入 quota、費用上限與 circuit breaker","linked_work_items":["AIA-SRE-013"],"terminal_condition":"每日、每月、每 incident 上限與 paired rollback 在付費呼叫前全部驗證。"},
|
||
{"id":"AIA-CONV-019","category":"ai_provider","status":"in_progress","title":"修復 Ollama timeout、Gemini/NIM unavailable、rate-limit 與重試風暴","linked_work_items":["AIA-SRE-013"],"terminal_condition":"bounded timeout/retry、same-domain circuit 與 provider failure card 在 replay 中穩定。"},
|
||
{"id":"AIA-CONV-020","category":"ai_provider","status":"source_implemented_runtime_pending","title":"每張告警列出使用的 AI、Agent、診斷、執行、驗證、token 與成本","linked_work_items":["AIA-SRE-013","AIA-SRE-017"],"terminal_condition":"recipient-visible card 只顯示 receipt-backed attribution，未觀測元件不得假性列出。"},
|
||
|
||
{"id":"AIA-CONV-021","category":"telegram","status":"in_progress","title":"盤點全部 Telegram 群組、BOT、產品與既有告警去向","linked_work_items":["AIA-SRE-017"],"terminal_condition":"每個 product/signal/severity 只有一個 canonical destination owner。"},
|
||
{"id":"AIA-CONV-022","category":"telegram","status":"in_progress","title":"建立唯一 destination ownership 與 alert routing matrix","linked_work_items":["AIA-SRE-017"],"terminal_condition":"未知 product/signal/destination fail closed，禁止 numeric destination default 與多群組噴發。"},
|
||
{"id":"AIA-CONV-023","category":"telegram","status":"source_implemented_runtime_pending","title":"WOOO BOT 的 Host188、StockPlatform 等告警改送 AwoooI SRE 戰情室","linked_work_items":["AIA-SRE-017"],"terminal_condition":"production delivery receipt 證明 canonical war-room destination，舊 BOT 不再收到營運告警。"},
|
||
{"id":"AIA-CONV-024","category":"telegram","status":"source_implemented_runtime_pending","title":"TsenYang BOT 的 Alertmanager/backup 告警改送 AwoooI SRE 戰情室","linked_work_items":["AIA-SRE-017"],"terminal_condition":"production delivery receipt 證明 canonical war-room destination，舊 BOT 不再收到該類告警。"},
|
||
{"id":"AIA-CONV-025","category":"telegram","status":"source_implemented_runtime_pending","title":"每張告警第一屏顯示明確分類","linked_work_items":["AIA-SRE-017"],"terminal_condition":"category、domain、severity、asset 與 lifecycle state 在首屏可辨識。"},
|
||
{"id":"AIA-CONV-026","category":"telegram","status":"source_implemented_runtime_pending","title":"告警改為管理者可快速判讀的精簡視覺化卡片","linked_work_items":["AIA-SRE-017"],"terminal_condition":"卡片呈現影響、AI 動作、結果、阻擋與唯一下一安全動作，移除重複長文。"},
|
||
{"id":"AIA-CONV-027","category":"telegram","status":"source_implemented_runtime_pending","title":"修復重啟、擴縮容、回滾、清快取等無效按鈕","linked_work_items":["AIA-SRE-017"],"terminal_condition":"每個顯示按鈕都有 registry action、授權、callback、executor/verifier 或 fail-closed receipt。"},
|
||
{"id":"AIA-CONV-028","category":"telegram","status":"source_implemented_runtime_pending","title":"串通 callback ingress、dispatch、verifier 與 durable action receipt","linked_work_items":["AIA-SRE-009","AIA-SRE-015","AIA-SRE-017"],"terminal_condition":"recipient callback 與 same-run controlled action receipt 可由 production readback 證明。"},
|
||
{"id":"AIA-CONV-029","category":"telegram","status":"source_implemented_runtime_pending","title":"AwoooI SRE 戰情室 Bot 自動理解並正確回覆使用者訊息","linked_work_items":["AIA-SRE-012","AIA-SRE-013","AIA-SRE-017"],"terminal_condition":"群組訊息經身份、意圖、RAG 與 policy 後產生可追溯回覆，不接受未授權 runtime mutation。","source_evidence":["telegram group text durable ingress receipt","deterministic intent classification","bounded sanitized KM/RAG retrieval","traceable no-runtime-mutation provider receipt"]},
|
||
{"id":"AIA-CONV-030","category":"telegram","status":"source_implemented_runtime_pending","title":"對話可啟動受控調查/修復並建立 Codex 開發 work item","linked_work_items":["AIA-SRE-001","AIA-SRE-015","AIA-SRE-017"],"terminal_condition":"討論結果轉為去重 work item；production action 仍走 typed executor/verifier。","source_evidence":["verified controlled_action_request ingress gate","exact canonical asset/domain resolution or asset_identity_unresolved drift item","fingerprint-deduplicated durable internal work-item receipt","deterministic no-provider no-runtime-mutation Telegram response"]},
|
||
{"id":"AIA-CONV-031","category":"telegram","status":"source_implemented_runtime_pending","title":"同 fingerprint 去重、聚合、抑噪及 resolved/recovered 更新","linked_work_items":["AIA-SRE-017"],"terminal_condition":"同事件只維護 canonical lifecycle，恢復卡有 destination-bound provider acknowledgement。","source_evidence":["existing firing fingerprint convergence and parent-child alert storm aggregation","single-row durable resolved lifecycle reservation with bounded retry","duplicate resolved webhook suppression before incident or Telegram side effects","recovery card accepted only with destination-bound provider acknowledgement"]},
|
||
|
||
{"id":"AIA-CONV-032","category":"named_incident","status":"source_implemented_runtime_pending","title":"INC-20260711-11C751 cold-start-gate 補 PlayBook、transport、rollback 與 verifier","linked_work_items":["AIA-SRE-004","AIA-SRE-006","AIA-SRE-015"],"terminal_condition":"namespace identity 修正後完成一次 bounded same-run repair 或明確 no-write terminal。","source_evidence":["source namespace separated from normalized host_recovery execution identity","exact inventory scope absence blocks Recover before single-flight claim or Agent99 transport","durable alert operation receipt records the explicit no-write terminal","consumer-validated source no-write verifier receipt with runtime closure false"]},
|
||
{"id":"AIA-CONV-033","category":"named_incident","status":"source_implemented_runtime_pending","title":"INC-20260711-D037E5 修復 stale candidate 阻擋、自動排隊與 durable closure","linked_work_items":["AIA-SRE-007","AIA-SRE-015"],"terminal_condition":"新候選可 claim，apply 不重複，verifier、Telegram 與 learning receipts 同 run 完成。","source_evidence":["D037E5 canonical workload identity resolves to the Kubernetes executor/verifier without consulting legacy Ansible candidates","fingerprint-stable durable candidate event supports pending and pre-dispatch lease-expired atomic claim","dedicated feature-gated Kubernetes executor job owns a bounded one-candidate claim tick and is not started by API, signal worker or Ansible broker","single-dispatch barrier suppresses duplicate apply after dispatch starts","durable closure requires lifecycle, independent verifier, Telegram provider acknowledgement and learning receipts on one execution run"]},
|
||
{"id":"AIA-CONV-034","category":"named_incident","status":"source_implemented_runtime_pending","title":"AWOOOI CPU 高負載與 P99 上升完成 RCA、bounded repair 與 verifier","linked_work_items":["AIA-SRE-004","AIA-SRE-006","AIA-SRE-010"],"terminal_condition":"相關 metrics/logs/changes 對齊 canonical asset，修復後 latency 與資源 verifier 關閉。","source_evidence":["same-run canonical CPU/P99 metrics, sanitized log and recent-change receipt correlation","exact typed Kubernetes, Host Ansible and database RCA lanes with unknown-asset fail-closed behavior","fingerprint-deduplicated durable candidate receipt without provider, Agent99 or runtime mutation","durable closure requires typed execution plus deterministic independent resource and SigNoz P99 verifier receipts on one run"]},
|
||
{"id":"AIA-CONV-035","category":"named_incident","status":"source_implemented_runtime_pending","title":"Backup/restore escrow 補 freshness、escrow metadata、restore drill 與 DR scorecard","linked_work_items":["AIA-SRE-011","AIA-SRE-016"],"terminal_condition":"read-only evidence 齊全；缺 escrow/restore receipt 時保持 blocked 而非假綠。","source_evidence":["same-run public-safe backup status, freshness, offsite, escrow and restore-drill metadata receipts","freshness RPO plus isolated restore-drill RTO deterministic gates","metadata-only escrow with no secret value and no runtime mutation boundary","DR scorecard remains blocked until every durable evidence receipt verifies"]},
|
||
{"id":"AIA-CONV-036","category":"named_incident","status":"source_implemented_runtime_pending","title":"Sentry Snuba DockerContainerUnhealthy 反覆告警自動修復","linked_work_items":["AIA-SRE-005"],"terminal_condition":"exact-container replay 完成 bounded recovery、健康 verifier 與 recurrence fence。"},
|
||
{"id":"AIA-CONV-037","category":"named_incident","status":"source_implemented_runtime_pending","title":"AlertChainBroken_Alertmanager webhook error 大於 10% 自動旁路與修復","linked_work_items":["AIA-SRE-014","AIA-SRE-017"],"terminal_condition":"integration-scoped counters、旁路 delivery、receiver contract 與恢復 receipt 全部成立。"},
|
||
{"id":"AIA-CONV-038","category":"named_incident","status":"source_implemented_runtime_pending","title":"provider_freshness_signal 改成 readback、repair 與 verify","linked_work_items":["AIA-SRE-013","AIA-SRE-017"],"terminal_condition":"provider window、last seen、direct reference 與 no-false-green verifier 決定 terminal。"},
|
||
{"id":"AIA-CONV-039","category":"named_incident","status":"source_implemented_runtime_pending","title":"Backup.awoooi-frequent、Langfuse、Signoz、AI 等 backup family 分類與閉環","linked_work_items":["AIA-SRE-011","AIA-SRE-017"],"terminal_condition":"每類 backup signal 有正確 route、read-only receipt、去重與 closure。"},
|
||
{"id":"AIA-CONV-040","category":"named_incident","status":"source_implemented_runtime_pending","title":"Host188 PostgreSQL CPU、長查詢、MOMO provider backoff 由 Agent99 處置","linked_work_items":["AIA-SRE-006","AIA-SRE-010"],"terminal_condition":"typed Host188/DB dispatch、bounded apply、獨立 verifier 與 recipient receipt 完成。"},
|
||
{"id":"AIA-CONV-041","category":"named_incident","status":"source_implemented_runtime_pending","title":"StockPlatform cron_intelligence_sync 連續失敗自動診斷、修正與驗證","linked_work_items":["AIA-SRE-004","AIA-SRE-006"],"terminal_condition":"wrapped-command/root cause 修正後 cron freshness 與 exit-code verifier 關閉。","source_evidence":["exact StockPlatform cron_intelligence_sync schedule identity fails closed without cross-domain fallback","same-run durable failure, sanitized wrapped-command RCA and exact source-fix receipts create one fingerprint-deduplicated candidate","local or unreachable source commit remains release-pending and cannot invoke a provider, Agent99, executor or runtime mutation","durable runtime closure requires exact controlled deployment plus independent exit-code and freshness receipts from one deployment run"]},
|
||
|
||
{"id":"AIA-CONV-042","category":"knowledge_closure","status":"in_progress","title":"所有告警推理前整合 MCP 與 RAG context","linked_work_items":["AIA-SRE-012","AIA-SRE-015"],"terminal_condition":"每次推理記錄 context source IDs、freshness 與 retrieval receipt。"},
|
||
{"id":"AIA-CONV-043","category":"knowledge_closure","status":"source_implemented_runtime_pending","title":"診斷、候選、執行、驗證沉澱至 KM/RAG/MCP/PlayBook","linked_work_items":["AIA-SRE-015"],"terminal_condition":"同 run 六個 durable write receipts 唯一、可讀回且與 target/source 一致。"},
|
||
{"id":"AIA-CONV-044","category":"knowledge_closure","status":"source_implemented_runtime_pending","title":"每項資產必須有 ID、owner、status、next action、來源與 receipt","linked_work_items":["AIA-SRE-001","AIA-SRE-002","AIA-SRE-015"],"terminal_condition":"Runs、Work Items 與 KB 只讀同一 canonical identity 與 evidence chain。"},
|
||
{"id":"AIA-CONV-045","category":"knowledge_closure","status":"in_progress","title":"24 小時 production 告警形成可學習 corpus","linked_work_items":["AIA-SRE-016"],"terminal_condition":"alert、repair、execution、verifier、recurrence 與 cost 分母可重算，shadow 不冒充 execution。"},
|
||
{"id":"AIA-CONV-046","category":"knowledge_closure","status":"source_implemented_runtime_pending","title":"Runs、Work Items、Knowledge Base 顯示完整關聯證據","linked_work_items":["AIA-SRE-001","AIA-SRE-015","AIA-SRE-017"],"terminal_condition":"API 與 desktop/mobile cockpit 對相同 run 顯示一致的資產與 receipt truth。"},
|
||
{"id":"AIA-CONV-047","category":"knowledge_closure","status":"in_progress","title":"Executor 不得是唯一 verifier","linked_work_items":["AIA-SRE-014"],"terminal_condition":"每個 mutating domain 都有不同 owner/identity 的 independent verifier。"},
|
||
{"id":"AIA-CONV-048","category":"knowledge_closure","status":"source_implemented_runtime_pending","title":"Telegram、callback、learning receipt 使用 durable production readback","linked_work_items":["AIA-SRE-015","AIA-SRE-017"],"terminal_condition":"source flag、HTTP 200 或 configured state 不得取代 production durable acknowledgement。"},
|
||
|
||
{"id":"AIA-CONV-049","category":"infrastructure","status":"source_implemented_runtime_pending","title":"Host112 開機、Guest 與 Wazuh 狀態由 Agent99 VMware typed check、bounded recovery 與 verifier 閉環","linked_work_items":["AIA-SRE-006","AIA-SRE-009"],"terminal_condition":"同一 Agent99 run 取得 canonical VMX power、guest readiness、boot identity、Wazuh 與獨立 verifier durable receipt；不做任意命令。"},
|
||
{"id":"AIA-CONV-050","category":"infrastructure","status":"source_implemented_runtime_pending","title":"Host110 Ollama 退役後清除 inventory、health check、fallback 與告警來源","linked_work_items":["AIA-SRE-002","AIA-SRE-004"],"terminal_condition":"保留 retired tombstone；任何 process/proxy/listener/target/route recurrence 建 drift item。"},
|
||
{"id":"AIA-CONV-051","category":"infrastructure","status":"in_progress","title":"Host111 Ollama 補健康度、模型、LaunchAgent 與容量證據","linked_work_items":["AIA-SRE-002","AIA-SRE-008","AIA-SRE-013"],"terminal_condition":"host111 本機與 host120/121 獨立 origin 讀回 exact model、service 與 sensor。"},
|
||
{"id":"AIA-CONV-052","category":"infrastructure","status":"source_implemented_runtime_pending","title":"Host99 Agent99 串入 typed dispatch、主機操作、rollback 與 verifier","linked_work_items":["AIA-SRE-006","AIA-SRE-009","AIA-SRE-014"],"terminal_condition":"production allowlisted run 與 cross-domain denial 都有同 run callback/receipt。"},
|
||
{"id":"AIA-CONV-053","category":"infrastructure","status":"in_progress","title":"查核 infrastructure_inventory.md 的遺漏與過期資訊","linked_work_items":["AIA-SRE-001","AIA-SRE-002"],"terminal_condition":"每個 imported/omitted asset 與 live canonical registry 對帳並標示 drift。"},
|
||
{"id":"AIA-CONV-054","category":"infrastructure","status":"not_started_or_no_current_evidence","title":"將盤點套用到所有專案、產品、網站及其 AI Agent 自動化","linked_work_items":["AIA-SRE-001","AIA-SRE-002","AIA-SRE-014"],"terminal_condition":"所有在管產品都有 asset、monitor、route、executor、verifier 與 owner coverage。"},
|
||
{"id":"AIA-CONV-055","category":"infrastructure","status":"in_progress","title":"建立 project/product 到 asset、monitor、alert、Telegram、executor/verifier 的 canonical mapping","linked_work_items":["AIA-SRE-001","AIA-SRE-002","AIA-SRE-017"],"terminal_condition":"mapping 可 machine-read、去重、fail closed，且 production exact mirror 可驗證。"},
|
||
|
||
{"id":"AIA-CONV-056","category":"work_management","status":"source_implemented_runtime_pending","title":"建立完整工作總帳並補足 18 項父台帳未展開的承諾","linked_work_items":["AIA-SRE-001"],"terminal_condition":"本 registry 70 項由 API 完整讀回且 rollup 與 committed source 一致。"},
|
||
{"id":"AIA-CONV-057","category":"work_management","status":"in_progress","title":"定義全部 P0/P1、依賴與 critical path，避免修 A 壞 B/C/D","linked_work_items":["AIA-SRE-001","AIA-SRE-018"],"terminal_condition":"子承諾繼承父工項 priority/order；不建立第二套互相衝突 queue。"},
|
||
{"id":"AIA-CONV-058","category":"work_management","status":"source_implemented_runtime_pending","title":"顯示完成、進行中、未完成與可信百分比","linked_work_items":["AIA-SRE-001","AIA-SRE-016"],"terminal_condition":"source progress 與 runtime closure 分開計算，百分比不可假綠。"},
|
||
{"id":"AIA-CONV-059","category":"work_management","status":"in_progress","title":"外來工作不得阻塞原主線，必要事故處理後立即返回","linked_work_items":["AIA-SRE-001"],"terminal_condition":"delegation 只能補 immediate dependency evidence，不能改 current_p0 或 queue。"},
|
||
{"id":"AIA-CONV-060","category":"work_management","status":"superseded","title":"分階段同步其他工作視窗","linked_work_items":["AIA-SRE-001"],"terminal_condition":"已被禁止未授權跨 task 訊息取代。","superseded_by":"AIA-CONV-059"},
|
||
{"id":"AIA-CONV-061","category":"work_management","status":"in_progress","title":"Wazuh 首屏正確區分 manager posture 18/18 與整體 runtime 0%","linked_work_items":["AIA-SRE-001","AIA-SRE-017"],"terminal_condition":"production desktop/mobile 首屏標籤範圍清楚，無 console error 或 overflow。"},
|
||
|
||
{"id":"AIA-CONV-062","category":"delivery_efficiency","status":"in_progress","title":"異常、合約錯誤與 blocker 做 bounded 修正後立刻回主線","linked_work_items":["AIA-SRE-018"],"terminal_condition":"只處理會阻擋 immediate next action 的精確根因，不建立旁支。"},
|
||
{"id":"AIA-CONV-063","category":"delivery_efficiency","status":"analysis_or_governance_complete","title":"先做 focused local test、contract 與 replay，不靠 CD 猜問題","linked_work_items":["AIA-SRE-018"],"terminal_condition":"工作方法已由 Governance v3 啟用；每個 source candidate 持續遵守。"},
|
||
{"id":"AIA-CONV-064","category":"delivery_efficiency","status":"analysis_or_governance_complete","title":"每個 candidate 預設一次正常整合，禁止空 commit 與連續 CD 重試","linked_work_items":["AIA-SRE-018"],"terminal_condition":"工作方法已啟用；下一次整合必須有新 source 或 transient 證據。"},
|
||
{"id":"AIA-CONV-065","category":"delivery_efficiency","status":"analysis_or_governance_complete","title":"queue、CD、rollout 等等待交給 watcher，禁止模型前景輪詢","linked_work_items":["AIA-SRE-018"],"terminal_condition":"工作方法已啟用；等待不產生重複模型回報。"},
|
||
{"id":"AIA-CONV-066","category":"delivery_efficiency","status":"in_progress","title":"source/test、CD/deploy、runtime、recipient-visible proof 分層回報","linked_work_items":["AIA-SRE-018"],"terminal_condition":"任何低層證據不得提升未完成的高層狀態。"},
|
||
{"id":"AIA-CONV-067","category":"delivery_efficiency","status":"in_progress","title":"以 tokens per verified completion 控制 Token 效率","linked_work_items":["AIA-SRE-001","AIA-SRE-018"],"terminal_condition":"避免重讀、發散、輪詢與無狀態回報，同時保留必要測試與 verifier。"},
|
||
{"id":"AIA-CONV-068","category":"delivery_efficiency","status":"superseded","title":"由本視窗修復 CI/CD","linked_work_items":["AIA-SRE-018"],"terminal_condition":"已被另一工作視窗負責 CI/CD、本視窗續推原工作取代。","superseded_by":"AIA-CONV-062"},
|
||
{"id":"AIA-CONV-069","category":"delivery_efficiency","status":"analysis_or_governance_complete","title":"Codex Governance v3 生效且 delegation 不得改寫 current P0","linked_work_items":["AIA-SRE-001"],"terminal_condition":"active instructions 已生效；後續 source work 持續遵守。"},
|
||
{"id":"AIA-CONV-070","category":"delivery_efficiency","status":"in_progress","title":"稽核所有已變更內容是否真正推至 production","linked_work_items":["AIA-SRE-018"],"terminal_condition":"每批以 exact source、CD terminal、deploy marker、runtime 與 recipient-visible readback 驗收。"}
|
||
],
|
||
"rollups": {
|
||
"total_commitments": 70,
|
||
"active_or_completed_commitments": 68,
|
||
"by_status": {
|
||
"analysis_or_governance_complete": 6,
|
||
"source_implemented_runtime_pending": 34,
|
||
"in_progress": 27,
|
||
"not_started_or_no_current_evidence": 1,
|
||
"superseded": 2
|
||
},
|
||
"product_runtime_closed_commitments": 0
|
||
}
|
||
}
|