skills
/
deerflow2
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(01): sync research notes and remove stale validation draft

This commit is contained in:
肖应宇 2026-04-07 14:30:53 +08:00
parent eb8f979e1b
commit d12fb11993
2 changed files with 3 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.planning/phases/01-conflict-inventory-and-decision-matrix/01-RESEARCH.md
View File

@ -208,19 +208,17 @@ P2: < 0.50
| A3 | “作者轨 + 语义轨”双轨识别足以覆盖 Titan overlap | Pitfall 2 | 可能漏判少量逻辑来源 | | A3 | “作者轨 + 语义轨”双轨识别足以覆盖 Titan overlap | Pitfall 2 | 可能漏判少量逻辑来源 |
| A4 | L0/L1/L2 三层拆分能稳定隔离视觉与逻辑 | Pattern 3 | 若耦合过深，执行成本上升 | | A4 | L0/L1/L2 三层拆分能稳定隔离视觉与逻辑 | Pattern 3 | 若耦合过深，执行成本上升 |
## Open Questions (RESOLVED) ## Open Questions
1. **Titan overlap 的“最终裁决权”落在谁** 1. **Titan overlap 的“最终裁决权”落在谁**
- What we know: 已可机械识别 overlap 文件与提交来源。[VERIFIED: git 证据链] - What we know: 已可机械识别 overlap 文件与提交来源。[VERIFIED: git 证据链]
- What's unclear: 业务上遇到冲突时由谁决定 keep/replace（产品、前端 owner、原作者）。[ASSUMED] - What's unclear: 业务上遇到冲突时由谁决定 keep/replace（产品、前端 owner、原作者）。[ASSUMED]
- Resolution: 已在 `01-PLAN.md` 的执行约束中落地为“决策矩阵必须含 rationale 与阶段归属，并形成可审计输出”，默认由当前仓库维护 owner 在 Phase 01 产物评审时裁决。[VERIFIED: `01-PLAN.md`] - Recommendation: 在 planner 阶段把“裁决角色 + SLA”写入 PLAN.md，避免执行阻塞。[ASSUMED]
- Status: RESOLVED
2. **`content_id` vs `content_ids` 的阶段边界** 2. **`content_id` vs `content_ids` 的阶段边界**
- What we know: 该协议冲突属于 Phase 2（LOGIC-04），但 Phase 1 需要在矩阵中标红相关文件。[VERIFIED: `.planning/ROADMAP.md`, `.planning/REQUIREMENTS.md`] - What we know: 该协议冲突属于 Phase 2（LOGIC-04），但 Phase 1 需要在矩阵中标红相关文件。[VERIFIED: `.planning/ROADMAP.md`, `.planning/REQUIREMENTS.md`]
- What's unclear: Phase 1 是否要提前定义兼容窗口（双写/双读）。[ASSUMED] - What's unclear: Phase 1 是否要提前定义兼容窗口（双写/双读）。[ASSUMED]
- Resolution: Phase 1 明确只做证据与决策输入，不提前实施协议兼容；兼容窗口设计下沉到 Phase 2 执行计划。[VERIFIED: `01-PLAN.md`, `.planning/ROADMAP.md`] - Recommendation: 在 Phase 1 仅标注风险与影响范围，不提前改实现。[ASSUMED]
- Status: RESOLVED
## Environment Availability ## Environment Availability

28
.planning/phases/01-conflict-inventory-and-decision-matrix/01-VALIDATION.md
View File

@ -1,28 +0,0 @@
# Phase 01 Validation
**Phase:** 01 - conflict-inventory-and-decision-matrix
**Date:** 2026-04-07
**Language:** zh-CN
## Validation Scope
本文件用于满足 Nyquist 验证门要求，定义 Phase 01 计划任务与自动化验证命令的映射关系，确保交付物可测、可复现、可审计。
## Task-to-Validation Mapping
| Task | Requirement | Artifact | Automated Validation | Pass Condition |
|------|-------------|----------|----------------------|----------------|
| Wave 1 / Task 1 | MERGE-01 | `audit-evidence.md` | `test -s .planning/phases/01-conflict-inventory-and-decision-matrix/audit-evidence.md && rg -n "git show -m|git log --all --author='\\[Tt\\]itan'|7342cc08|merge" .planning/phases/01-conflict-inventory-and-decision-matrix/audit-evidence.md` | 文档存在且包含证据命令链关键字 |
| Wave 2 / Task 2 | MERGE-01 | `conflict-inventory.csv`, `conflict-inventory.md` | `test -s .planning/phases/01-conflict-inventory-and-decision-matrix/conflict-inventory.csv && test -s .planning/phases/01-conflict-inventory-and-decision-matrix/conflict-inventory.md && head -n 1 .planning/phases/01-conflict-inventory-and-decision-matrix/conflict-inventory.csv | rg "file_path,merge_hotspot_count,titan_touch_count,change_class,behavior_critical,risk_level,evidence_refs" && rg -n "P0|P1|P2|visual-only|logic-only|mixed" .planning/phases/01-conflict-inventory-and-decision-matrix/conflict-inventory.md` | CSV 列头完整、分级规则存在 |
| Wave 3 / Task 3 | MERGE-03 | `titan-decision-matrix.md` | `test -s .planning/phases/01-conflict-inventory-and-decision-matrix/titan-decision-matrix.md && rg -n "keep|replace|hybrid|L0|L1|L2|Phase 2|Phase 3|rationale" .planning/phases/01-conflict-inventory-and-decision-matrix/titan-decision-matrix.md` | 每条决策至少具备 decision/rationale/phase mapping |
## Nyquist Gate Checklist
- [x] 计划任务均有自动化验证命令
- [x] 自动化验证命令可判定成功/失败
- [x] 验证覆盖 MERGE-01 与 MERGE-03 对应交付
- [x] 产物可作为后续 Phase 2/3 输入
## Exit Criteria
当且仅当三条 Task-to-Validation 映射对应命令全部通过，且抽查证据引用可追溯时，Phase 01 视为验证通过。