Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
> **Status: deferred 2026-07-28**(使用者裁決)。不計入 active WIP;解凍前不做實作。48/49 task 未動工且無任何實作 commit;依 2026-07-28 read-only 盤點分類:(a) **機制層已被既有落地取代**——冪等/指紋對齊階梯=`governance-service/diff_engine/keys.py`(`model-version-diff-authority`)、「人審 gate、不自動建 issue」語意=a4 change tasks 4.x/5.5+PR #398、BCFzip serializer 骨架=`bcf/bcf_writer.py`(BCF 2.1,`governance-bcf-export`)、checker→批次 issue 骨架=`rule_engine/`(`governance-rule-run-authority`)、task 7.5 凍結三檔回歸=repo 常設鐵律;(b) **真正無人認領的獨有主線**=Phase 0 GPU 量測 harness(1.1–1.5)與 2.11 無互動回收倒數,規劃另切小 change(暫名 `gpu-session-baseline-and-idle-reclaim`)承接,屆時對本 change 做 requirement/successor crosswalk;(c) IfcClash/LLM 草稿管線、人審 triage 佇列、BCF-API 3.0 端點維持凍結待裁。重啟條件:T1 小 change 落地後 thaw 做 crosswalk,或使用者明確 thaw;重啟時須重跑 `npx openspec validate add-single-gpu-session-ai-review-mvp --strict` 並重驗上列 supersede 證據仍成立。

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

使用明確的 successor change ID,避免 thaw 條件歧義。

此段先命名 gpu-session-baseline-and-idle-reclaim,後續卻改稱「T1 小 change」;若 T1 不是既有正式別名,解凍條件可能無法判定。請直接使用完整 change ID,或在此明確定義 T1。

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@openspec/changes/add-single-gpu-session-ai-review-mvp/proposal.md` at line 1,
Update the thaw condition in the change status note to consistently use the
explicit successor change ID gpu-session-baseline-and-idle-reclaim instead of
the ambiguous “T1” label. Preserve the requirement to complete that successor
change before thawing and performing the crosswalk, while retaining the separate
explicit-user-thaw alternative.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

npx openspec validate --all --strict

Repository: monkey1sai/AI-BIM-governance

Length of output: 643


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Tracked files mentioning openspec status/validation:"
rg -n "npx openspec validate|Status: deferred|Status: active|npx openspec validate --all --strict" -S . || true

echo
echo "Target proposal relevant status lines:"
sed -n '1,40p' openspec/changes/add-single-gpu-session-ai-review-mvp/proposal.md

echo
echo "Package manager files:"
git ls-files | rg '(^|/)(package.json|package-lock.json|pnpm-lock.yaml|yarn.lock|bun.lockb)$' || true

echo
echo "Top-level package scripts:"
if [ -f package.json ]; then
  cat package.json | python3 -c 'import json,sys; d=json.load(sys.stdin); print("scripts:", d.get("scripts",{}), "devDependencies:", {k:v for k,v in d.get("devDependencies",{}).items() if "openspec" in k.lower() or "codex" in k.lower()}, "dependencies:", {k:v for k,v in d.get("dependencies",{}).items() if "openspec" in k.lower() or "codex" in k.lower()})'
fi

Repository: monkey1sai/AI-BIM-governance

Length of output: 14433


補齊 npx openspec validate --all --strict 驗證結果。

此 deferred change 的重啟條件和 repo guideline 都要求全 repository strict validation;目前 proposal 僅記錄 change-specific validation。請補跑並將結果記錄到重啟條件,或直接由具備 npm/openspec 環境者提供通過證據。

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@openspec/changes/add-single-gpu-session-ai-review-mvp/proposal.md` at line 1,
補跑全 repository 的 `npx openspec validate --all --strict`,並將實際通過或失敗結果記錄到
proposal.md 的重啟條件;同時保留既有 change-specific strict validation 要求,若無法執行則明確記錄缺少
npm/openspec 環境,不要宣稱已通過。

Source: Coding guidelines

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the unimplemented SessionBroker scope

When this deferred change is later split, this inventory will drop the core Phase 1 work: tasks 2.1–2.10 are all unchecked, and a repo-wide search finds no SessionBroker, SingleGpuDriver, or equivalent implementation, yet the new status says the only genuinely unowned track is Phase 0 plus task 2.11 and proposes gpu-session-baseline-and-idle-reclaim as the successor. Admission control, the primary queue, TTL/health recovery, and cold-start polling consequently have no stated future owner, allowing the proposal's primary user goal to silently fall out of planning; include these gaps in the frozen/unowned classification or assign them to an explicit successor.

AGENTS.md reference: AGENTS.md:L131-L139

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep AI issue idempotency marked as unimplemented

For cross-version AI findings, diff_engine/keys.py only aligns IFC elements by GlobalId, Tag, or type/name/location; it does not implement unchecked tasks 4.1–4.6's calibrated rule-plus-geometry fingerprints, guid_churn_suspected human routing, parent/child convergence, resolved/reopen lineage, or four-way difference report, and a repo-wide search finds no equivalent implementation. Classifying the fingerprint mechanism as already replaced while omitting issue-idempotency from the frozen tracks can therefore cause a later successor crosswalk to discard an entire unimplemented capability as superseded; retain it explicitly as frozen/unowned or name its actual successor.

AGENTS.md reference: AGENTS.md:L131-L139

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Retain the approved BCF 3.0 serializer work

The cited bcf/bcf_writer.py is not a replacement for task 6.4: both its implementation and the canonical governance-bcf-export spec explicitly emit BCF 2.1, while the proposed BCF-XML 3.0 serializer, official-XSD validation, JSON/BCFzip consistency check, and desktop-tool smoke remain entirely unchecked. Because the new inventory treats the 2.1 skeleton as replaced mechanism and only names BCF-API 3.0 endpoints—not the separately approved BCF-XML 3.0 archive—as frozen, a future crosswalk can silently lose this user-approved deliverable; list the 3.0 serializer explicitly as retained work or assign it to a successor.

AGENTS.md reference: AGENTS.md:L131-L139

Useful? React with 👍 / 👎.


## Why

使用者首要目標是「穩定多 session、單 GPU 的生命週期」,其上再疊加「AI 產草稿 → 人審轉正」的最小審查閉環,Kit 定位為前期渲染 / 3D viewer / WebRTC 多人會議檢討。四個問題驅動本 change:
Expand Down
Loading