Repository navigation
docs(DEC-019/DEC-020): 签核 D-28/D-29 —— 全仓待签核归零 - #78
Merged
Merged
Conversation
业务方 2026-09-24 裁定:`D19: 1做 2接受 3做` · `D20: 1做 2接受`。 - DEC-019 → 签核号 **D-28**:采纳 **α(改判分器提示词)+ β(守卫升级)**,接受 §4 边界; - DEC-020 → 签核号 **D-29**:采纳 **α(判据改成「本次改动之前」)**,接受误拦风险(须配豁免 + 可统计)。⚠️ **签核前核实了两处「DEC 原文已过期」**(不照抄旧文): - `DEC-019` 的 **γ 已随 B4 落地** —— `eval/judge_refs.json` 有 8 条「D 金丝雀」, 含 3 条 `kind=stacked_non_answer`(C3/C13/C19)⇒ 原选项「α + γ 合并进 B4」**已不适用**; - `DEC-020` 的 **§7-3 已满足** —— KB `A2` 篇已把该门标为「半硬 —— 判据是会话级」,`A2-R15` 在位。 两份 DEC 的 §6/§7 转为**裁定记录**(原文保留不覆盖),含**认下的代价**: - D-28:α ≈ **4.9 万 token** · **一致率可能下降 = 仪器变准不是回归** · **β 眼下就是红的**(实施时二选一); - D-29:**α 会误拦**(须豁免 + 可统计)· **零 token 但是门禁改动** ⇒ 先写能红的测试。 锚点同步(`CLAUDE.md` + `ROADMAP.md`):**待签核 = 0**;当前唯一待办改成「**两份 DEC 的实施**」。 验证:锚点守卫 **exit 0**(它自 2026-09-24 起管着这两份文件)· **574 passed / 2 skipped**。 提交前两问: ① **有决策事项** —— 即本提交承载的 `DEC-019`/`DEC-020` 签核(**D-28/D-29**), 备选与代价已随其 §6.3/§7.2 记录; ② 本仓无 CHANGELOG 机制。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
业务方 2026-09-24 裁定:
D19: 1做 2接受 3做·D20: 1做 2接受。DEC-019判分器放行口径DEC-020门 2 判据范围⇒ 全仓待签核 = 0。
DEC-019的 γ 已随 B4 落地 ——eval/judge_refs.json里有 8 条「D 金丝雀」,含 3 条
kind=stacked_non_answer(C3/C13/C19)⇒ 原 §6-1 的选项「α + γ 合并进 B4」已不适用(B4 早跑完);
DEC-020的 §7-3 已满足 —— KBA2篇强度表已把该门标为「半硬 —— 判据是会话级」,且
A2-R15在位(5 处)⇒ 无需再动 KB。认下的代价(签核时预登记,不得复述成"没问题")
calibrate)· 一致率可能下降 = 仪器变准,不是回归 ·β 眼下就是红的(洞未修)⇒ 实施时二选一:先修 α 让它转绿 / 显式标"已知未修";
零 token,但是门禁改动 ⇒ 先写能红的测试。
两份 DEC 的 §6/§7 已转为裁定记录(原文保留不覆盖);
CLAUDE.md/ROADMAP.md同步为待签核 = 0,并把「当前唯一待办」改成两份 DEC 的实施。
验证
574 passed / 2 skipped · 锚点守卫 exit 0(该守卫自 2026-09-24 起管着这两份锚点文件)。