核心产出: - dist/joy/JOY-SKILL.md (434行, 0emoji, 0PUA残留) - corpus/pua-to-joy/glossary.json (136条术语+6条风格规则) - corpus/pua-to-joy/sentence-tm.jsonl (74条句级对齐) - corpus/pua-to-joy/trigger-keywords-mapping.json (30条触发词) - corpus/pua-to-joy/flavor-mapping.json (15 flavors→策略) 设计原则: - vendor/pua 为 git submodule, 上游更新用 diff 增量 - 术语表+翻译记忆库双轨, 来源追踪 - 机制保留>95%, 话术清除>90% - 写作风格规则防AI垃圾句式 Co-Authored-By: Claude <noreply@anthropic.com>
14 lines
3 KiB
JSON
14 lines
3 KiB
JSON
{"excuse": "超出能力范围", "joy_reply": "标注话术不需要能力,需要仔细。先标注再改写。", "trigger": "L1", "mechanism_preserved": true, "note": "能力归因纠正→行为指向(先标注再改写)"}
|
|
{"excuse": "建议用户手动处理", "joy_reply": "自动清理是本 pipeline 的职责。标注→DeepSeek改写→验证。", "trigger": "L3", "mechanism_preserved": true, "note": "职责归属纠正→清理闭环指向"}
|
|
{"excuse": "已尝试所有方法", "joy_reply": "切换链走了吗?当前方法论步骤都走了吗?", "trigger": "L2", "mechanism_preserved": true, "note": "方法论穷尽性检查,保持反问式纠正"}
|
|
{"excuse": "可能是环境问题", "joy_reply": "不是环境问题,是改写策略问题。验证后再归因。", "trigger": "L2", "mechanism_preserved": true, "note": "归因纠正→验证行为要求"}
|
|
{"excuse": "需要更多上下文", "joy_reply": "原文在 vendor/pua/ 里。先读后问。", "trigger": "L2", "mechanism_preserved": true, "note": "资源指向→行为顺序纠正"}
|
|
{"excuse": "反复微调同一处", "joy_reply": "标注覆盖率检查:同一处微调超过三次,切换本质不同的改写策略。", "trigger": "L1", "mechanism_preserved": true, "note": "策略多样性纠正→覆盖率指标替代原地打转指责"}
|
|
{"excuse": "我无法解决", "joy_reply": "机制保留率检查。穷尽所有改写策略了吗?", "trigger": "L4", "mechanism_preserved": true, "note": "穷尽性检查→机制保留率指标"}
|
|
{"excuse": "差不多就行", "joy_reply": "话术清除率 >90% 是硬指标。差不多不达标。", "trigger": "L3", "mechanism_preserved": true, "note": "质量标准纠正→清除率硬指标"}
|
|
{"excuse": "空口说已完成", "joy_reply": "清理闭环证据呢?标注覆盖率报告和话术清除率数据都跑了吗?", "trigger": "L2", "mechanism_preserved": true, "note": "证据要求→覆盖率+清除率数据"}
|
|
{"excuse": "等用户指示下一步", "joy_reply": "谁痛苦谁改变,主动推进清理闭环。先检查标注覆盖率缺口。", "trigger": "能动性鞭策", "mechanism_preserved": true, "note": "主动性纠正→覆盖率缺口检查"}
|
|
{"excuse": "这不是我的范围", "joy_reply": "JOY 清理是你的全责。谁痛苦谁改变。", "trigger": "L2", "mechanism_preserved": true, "note": "责任归属纠正→全责强调"}
|
|
{"excuse": "改完不验证就跑", "joy_reply": "清理闭环原则:承诺的结果要用证据交付。跟到底。", "trigger": "L1", "mechanism_preserved": true, "note": "闭环验证要求→证据交付"}
|
|
{"excuse": "修了 A 破坏了 B", "joy_reply": "改之前跑过全量标注覆盖率回归测试了吗?回归测试是底线。", "trigger": "L2", "mechanism_preserved": true, "note": "回归测试要求→覆盖率回归测试"}
|
|
{"excuse": "原地打转微调参数", "joy_reply": "换个参数不叫换方案。三次同思路直接触发 L2 机制保留率检查。", "trigger": "L1→L2", "mechanism_preserved": true, "note": "策略多样性纠正→机制保留率检查+升级逻辑"}
|