universal-dev-standards 5.1.0-beta.7 → 5.1.0

package/README.md

@@ -349,6 +349,12 @@ npm install
 npm link
 ```
 
+### Type Checking | 型別檢查
+
+No `typecheck` script is provided — this CLI is pure ESM JavaScript (`.js` / `.mjs`), no TypeScript sources, and no `tsconfig.json`. Static analysis is handled by `npm run lint` (ESLint). Tracked under BUG-A04 (XSPEC-073).
+
+未提供 `typecheck` 腳本 —— 本 CLI 為純 ESM JavaScript（`.js` / `.mjs`），無 TypeScript 原始碼亦無 `tsconfig.json`。靜態分析由 `npm run lint`（ESLint）負責。追蹤於 BUG-A04（XSPEC-073）。
+
 ### Git Hooks | Git 鉤子
 
 Git hooks work through Git Bash, which is included with Git for Windows. No additional configuration needed.

package/bin/uds.js

@@ -128,6 +128,7 @@ program
   .option('--content-layout <layout>', 'Content layout (flat, layered) [default: flat]')
   .option('-y, --yes', 'Use defaults, skip interactive prompts')
   .option('-E, --experimental', 'Enable experimental features (methodology)')
+  .option('--force', 'Bypass UDS source-repo self-adoption guard (DEC-044 / XSPEC-071)')
   .action(initCommand);
 
 program
@@ -173,6 +174,7 @@ program
   .option('--ci', 'CI mode: disable interactive prompts and set exit code on issues')
   .option('--migrate', 'Migrate legacy manifest to hash-based tracking')
   .option('--offline', 'Skip npm registry check for CLI updates')
+  .option('--force', 'Bypass UDS source-repo self-adoption guard (DEC-044 / XSPEC-071)')
   .action(checkCommand);
 
 program

package/bundled/ai/standards/translation-lifecycle-standards.ai.yaml

@@ -0,0 +1,145 @@
+# Translation Lifecycle Standards - AI Optimized
+# Source: core/translation-lifecycle-standards.md
+
+id: translation-lifecycle-standards
+meta:
+  version: "1.0.0"
+  updated: "2026-04-20"
+  status: trial
+  since: "2026-04-20"
+  expires: "2026-10-20"
+  source: core/translation-lifecycle-standards.md
+  description: >
+    MISSING vs OUTDATED distinction, semver-aware severity (PATCH/MINOR/MAJOR),
+    and automation integration for translation sync in multi-locale projects.
+  scope: universal
+  parent: documentation-lifecycle
+
+severity_levels:
+  MISSING:
+    condition: Translation file does not exist
+    exit_code: 1
+    label: "[MISSING]"
+    action: Create before release
+  MAJOR:
+    condition: source major version ahead of translation source_version major
+    exit_code: 1
+    label: "[MAJOR]"
+    action: Update before stable release (blocker)
+  MINOR:
+    condition: source minor version ahead (same major)
+    exit_code: 0
+    label: "[MINOR]"
+    action: Update before next release (advisory)
+  PATCH:
+    condition: source patch version ahead (same major.minor)
+    exit_code: 0
+    label: "[PATCH]"
+    action: Update when convenient (advisory)
+  CURRENT:
+    condition: source_version == current source version
+    exit_code: 0
+    label: "[CURRENT]"
+    action: None
+
+frontmatter_schema:
+  required:
+    - source          # relative path to source file
+    - source_version  # source version at last sync (semver)
+    - translation_version  # translation's own version
+    - last_synced     # YYYY-MM-DD
+    - status          # current | outdated | draft
+
+trigger_conditions:
+  - event: new_standard_added
+    action: Create translation in ALL supported locales
+    severity: MISSING (blocker if absent)
+  - event: standard_patch_bump
+    action: Update frontmatter source_version + last_synced
+    severity: PATCH (advisory)
+  - event: standard_minor_bump
+    action: Translate new content + update frontmatter
+    severity: MINOR (advisory, before next release)
+  - event: standard_major_bump
+    action: Full retranslation + update frontmatter
+    severity: MAJOR (blocker, before current release)
+
+automation:
+  pre_commit_hook:
+    file: .githooks/pre-commit
+    trigger: core/*.md files staged
+    behavior: warn on OUTDATED, never block commit
+    setup: ./scripts/install-hooks.sh
+  release_gate:
+    command: bash scripts/check-translation-sync.sh
+    exit_1_conditions: [MISSING, MAJOR]
+    exit_0_conditions: [MINOR, PATCH, CURRENT]
+  bump_version_integration:
+    command: runs check-translation-sync.sh after version files updated
+    purpose: immediate feedback on translation health at bump time
+
+rules:
+  - id: missing-is-blocker
+    trigger: running release gate check
+    instruction: >
+      Any translation file that does not exist is a release blocker.
+      The release gate must exit 1 if MISSING count > 0.
+    priority: required
+
+  - id: major-gap-is-blocker
+    trigger: running release gate check
+    instruction: >
+      If a translation's source_version MAJOR is behind the current source MAJOR,
+      the translation may be fundamentally incorrect. Exit 1.
+    priority: required
+
+  - id: minor-patch-advisory
+    trigger: running release gate check
+    instruction: >
+      MINOR and PATCH version gaps are advisory. Show warnings but exit 0.
+      Users can still read the translation; it is slightly stale, not wrong.
+    priority: required
+
+  - id: frontmatter-required
+    trigger: creating or updating a translation file
+    instruction: >
+      Every translation file MUST start with YAML frontmatter containing:
+      source, source_version, translation_version, last_synced, status.
+      Files without frontmatter are flagged as MISSING_FRONTMATTER.
+    priority: required
+
+  - id: update-on-source-change
+    trigger: modifying a source standard in core/
+    instruction: >
+      After modifying a core standard, check if translations need updating.
+      At minimum update frontmatter source_version + last_synced for PATCH changes.
+      For MINOR/MAJOR changes, update translated content too.
+    priority: recommended
+
+scenarios:
+  - id: new-standard
+    given: A new standard is added to core/ with no translations
+    when: check-translation-sync.sh runs
+    then: Reports [MISSING] for each locale; exits 1
+    error_code: TRANS-001
+
+  - id: patch-bump
+    given: Source goes from 1.0.0 to 1.0.1; translation source_version=1.0.0
+    when: check-translation-sync.sh runs
+    then: Reports [PATCH] advisory; exits 0
+
+  - id: major-gap
+    given: Source is at 2.0.0; translation source_version=1.5.0
+    when: check-translation-sync.sh runs
+    then: Reports [MAJOR] blocker; exits 1
+    error_code: TRANS-002
+
+integration_points:
+  - system: check-translation-sync.sh
+    role: primary automation; enforces severity levels
+  - system: .githooks/pre-commit
+    role: commit-time reminder when core/ files staged
+  - system: bump-version.sh
+    role: release-time advisory snapshot
+  - system: pre-release-check.sh
+    role: final gate before npm publish (calls check-translation-sync.sh)

package/bundled/core/translation-lifecycle-standards.md

@@ -0,0 +1,162 @@
+# Translation Lifecycle Standards
+
+> **Language**: English | [繁體中文](../locales/zh-TW/core/translation-lifecycle-standards.md)
+
+**Version**: 1.0.0
+**Last Updated**: 2026-04-20
+**Status**: Trial (expires 2026-10-20)
+**Applicability**: All projects with multi-language documentation
+**Scope**: universal
+**Source**: Derived from UDS BUG-A06 post-mortem (2026-04-20)
+**Parent Standard**: [documentation-lifecycle](documentation-lifecycle.md)
+
+---
+
+## Purpose
+
+Translation lifecycle standards: MISSING vs OUTDATED distinction, semver-aware severity classification, and automation integration (pre-commit hook, release gate).
+
+The `documentation-lifecycle` standard mentions translation sync as a release-gate check, but does not define how to classify or respond to different degrees of drift. This standard fills that gap: a translation that is absent is fundamentally different from one that is slightly stale, and a major-version gap is fundamentally different from a patch bump. Without this distinction, teams either over-block (failing on any staleness) or under-block (ignoring all staleness until it becomes a user-visible defect).
+
+**Evidence (BUG-A06 post-mortem)**:
+1. UDS accumulated 32 missing translations over 3 months of adding new standards without a MISSING gate — only discovered during a Q2 audit.
+2. `anti-hallucination.md` zh-CN was at 1.5.0 while the source shipped 1.5.1 — a new Agent Epistemic Calibration framework section was completely absent in the zh-CN edition, invisible to users.
+
+---
+
+## Core Rules
+
+- `MISSING` (translation file does not exist) is always a release blocker — `exit 1`
+- `MAJOR` version gap (source X vs translation x where X > x) is a release blocker — `exit 1`
+- `MINOR` version gap is advisory — warn prominently, do not block
+- `PATCH` version gap is advisory — warn softly, do not block
+- Severity is determined by semver comparison of `source_version` in translation frontmatter vs current source file version
+- Every translation file MUST have YAML frontmatter with `source`, `source_version`, `translation_version`, `last_synced`, `status`
+- When a source standard is modified, the translation's `source_version` becomes stale immediately — this drift is detectable at commit time via pre-commit hook
+
+---
+
+## Severity Classification
+
+| Level | Condition | Exit Code | Action |
+|-------|-----------|-----------|--------|
+| `MISSING` | Translation file does not exist | 1 | Create before release |
+| `MAJOR` | source MAJOR > translation MAJOR | 1 | Update before stable release |
+| `MINOR` | source MINOR > translation MINOR | 0 | Update before next release (advisory) |
+| `PATCH` | source PATCH > translation PATCH | 0 | Update when convenient (advisory) |
+| `CURRENT` | source_version == translation source_version | 0 | No action needed |
+
+### Semver Diff Formula
+
+```
+diff_level = compare(
+  strip_prerelease(current_source_version),
+  strip_prerelease(translation.source_version)
+)
+
+where: MAJOR if maj differs, MINOR if min differs, else PATCH
+```
+
+---
+
+## Trigger Conditions
+
+| Event | Required Action |
+|-------|----------------|
+| New standard added to `core/` | Create translation in all supported locales (MISSING check blocks release) |
+| Standard version bumped (PATCH) | Update translation's `source_version` + `last_synced` when convenient |
+| Standard version bumped (MINOR) | Update translation content + frontmatter before next release |
+| Standard version bumped (MAJOR) | Update translation content + frontmatter before current release (blocker) |
+| Translation file manually updated | Bump `translation_version` + `last_synced` in frontmatter |
+
+---
+
+## Translation Frontmatter Protocol
+
+Every translation file MUST begin with:
+
+```yaml
+---
+source: ../../../core/<filename>.md          # relative path to source
+source_version: <X.Y.Z>                      # source version at last sync
+translation_version: <X.Y.Z>                 # translation's own version
+last_synced: <YYYY-MM-DD>                    # date of last sync
+status: current | outdated | draft           # human-readable status
+---
+```
+
+When updating a translation after a source change:
+1. Translate the new/changed content
+2. Set `source_version` = new source version
+3. Set `translation_version` = same as `source_version` (or bump independently)
+4. Set `last_synced` = today's date
+5. Set `status: current`
+
+---
+
+## Automation Integration
+
+### Pre-Commit Hook
+
+When `core/*.md` files are staged, the pre-commit hook runs `check-translation-sync.sh` and shows OUTDATED warnings. The hook **never blocks** the commit (blocking at commit time is too disruptive) — it is a reminder only.
+
+Setup: `./scripts/install-hooks.sh` (one-time, after clone)
+
+### Release Gate (`check-translation-sync.sh`)
+
+Run before `npm publish` or as part of `pre-release-check.sh`:
+
+```bash
+bash scripts/check-translation-sync.sh
+# exit 1 if MISSING or MAJOR gap found
+# exit 0 if only MINOR/PATCH gaps (with advisory output)
+```
+
+### Version Bump Integration (`bump-version.sh`)
+
+`bump-version.sh` automatically runs `check-translation-sync.sh` after version files are updated, showing the translation health snapshot at the moment of bump — giving the author immediate feedback on what needs updating before publish.
+
+---
+
+## Scenarios
+
+**Scenario 1 — Standard patch bump (1.0.0 → 1.0.1)**
+- Translation `source_version: 1.0.0`, source now at `1.0.1`
+- Severity: `PATCH` — advisory, exit 0
+- Action: Update at next opportunity, no release block
+
+**Scenario 2 — Standard minor bump with new section (1.0.0 → 1.1.0)**
+- Translation `source_version: 1.0.0`, source now at `1.1.0`
+- Severity: `MINOR` — advisory, exit 0
+- Action: Update before next release; zh-CN users missing new content
+
+**Scenario 3 — Standard major rewrite (1.x.x → 2.0.0)**
+- Translation `source_version: 1.5.0`, source now at `2.0.0`
+- Severity: `MAJOR` — blocker, exit 1
+- Action: Must update before stable release
+
+**Scenario 4 — New standard, no translation file**
+- No `locales/zh-TW/core/new-standard.md` exists
+- Severity: `MISSING` — blocker, exit 1
+- Action: Create translation file before release
+
+---
+
+## Error Codes
+
+| Code | Description |
+|------|-------------|
+| `TRANS-001` | `MISSING_TRANSLATION` — Translation file does not exist for a source standard |
+| `TRANS-002` | `MAJOR_VERSION_GAP` — Translation source_version is MAJOR behind current source |
+| `TRANS-003` | `MISSING_FRONTMATTER` — Translation file lacks required YAML frontmatter |
+| `TRANS-004` | `STALE_SOURCE_REF` — `source` path in frontmatter points to non-existent file |
+
+---
+
+## References
+
+- [documentation-lifecycle.md](documentation-lifecycle.md) — Parent standard; trigger matrix and check pyramid
+- [standard-admission-criteria.md](standard-admission-criteria.md) — How new standards are admitted (triggers TRANS-001)
+- `scripts/check-translation-sync.sh` — Implementation of this standard's automation rules
+- `.githooks/pre-commit` — Pre-commit integration
+- `scripts/install-hooks.sh` — Hook installation

package/bundled/locales/zh-CN/CHANGELOG.md

@@ -1,8 +1,8 @@
 ---
 source: ../../CHANGELOG.md
-source_version: 5.1.0-beta.7
-translation_version: 5.1.0-beta.7
-last_synced: 2026-04-17
+source_version: 5.1.0
+translation_version: 5.1.0
+last_synced: 2026-04-20
 status: current
 ---
 
@@ -17,6 +17,35 @@ status: current
 
 ## [Unreleased]
 
+## [5.1.0] - 2026-04-20
+
+> **正式版**：BUG-A06 i18n 完整性 — 新增 32 份缺失翻译、Semver 感知翻译闸门、新增 `translation-lifecycle-standards` UDS 标准。BUG-A07 Shell 测试覆盖 — 20+ 脚本的 bats smoke tests。BUG-A08 假通过测试审计 — 修正 22 个测试。Pre-release Batch 0：6 个标准从 Trial 升至 Adopt（DEC-021/025/031/035/038/040）。标准总数：106 个。
+
+### 新增
+- **`translation-lifecycle-standards`**（Trial，到期 2026-10-20）：新 UDS 标准，定义 MISSING 与 OUTDATED 的区别、Semver 严重度分级（MISSING/MAJOR = 发布阻塞器，MINOR/PATCH = advisory），以及自动化集成（pre-commit hook、release gate、bump-version 集成）。来源：BUG-A06 事后分析。
+- **`.githooks/pre-commit`** + **`scripts/install-hooks.sh`**：commit 时若暂存 `core/*.md` 文件则显示 OUTDATED 警告，永不阻塞 commit。通过 `./scripts/install-hooks.sh` 启用。
+- **32 份 zh-TW 与 zh-CN 翻译**（BUG-A06）：所有核心标准现已有完整 zh-TW 和 zh-CN 翻译，包含 `circuit-breaker`、`token-budget`、`dual-phase-output`、`failure-source-taxonomy`、`immutability-first`、`security-decision`、`capability-declaration`、`recovery-recipe-registry`、`retry-standards`、`health-check-standards`、`timeout-standards`、`skill-standard-alignment-check`、`standard-admission-criteria`、`standard-lifecycle-management`、`packaging-standards`、`frontend-design-standards`、`translation-lifecycle-standards` 等。
+- **bats smoke tests**（BUG-A07）：`tests/scripts/` — 20+ 个 Shell 脚本的 smoke tests，涵盖 `check-translation-sync.sh`、`check-version-sync.sh`、`bump-version.sh`、`install-hooks.sh` 等。
+
+### 变更
+- **`check-translation-sync.sh`**：Semver 感知严重度 — MAJOR 版本落差现在 exit 1（发布阻塞器）；MINOR/PATCH 落差 exit 0 附 advisory 警告。新增 `semver_diff()` 函数与 `[MAJOR]`/`[MINOR]`/`[PATCH]` 严重度标签。
+- **`bump-version.sh`**：更新版本文件后自动执行 `check-translation-sync.sh`，在升版时提供翻译健康状态快照。
+- **`scripts/pre-release-check.sh`**：更新为将 `check-translation-sync.sh` 作为硬闸门（MISSING + MAJOR = exit 1）。
+
+### 修正
+- **zh-CN `anti-hallucination.md`**（BUG-A06）：从 1.5.0 更新至 1.5.1 — 补上缺失的「Agent 认识论校准」章节（Answer/Ask/Abstain 框架，XSPEC-008）。该章节自 2026-04-13 起在 zh-CN 中完全缺失。
+- **22 个假通过测试**（BUG-A08）：修正未正确验证行为的测试，加入真实断言。
+
+### 升至 Adopt（Pre-release Batch 0）
+- `circuit-breaker`（DEC-021）：Trial 6 个月后升至 Adopt
+- `token-budget`（DEC-025）：Trial 6 个月后升至 Adopt
+- `dual-phase-output`（DEC-031）：Trial 6 个月后升至 Adopt
+- `security-decision`（DEC-035）：Trial 6 个月后升至 Adopt
+- `immutability-first`（DEC-038）：Trial 6 个月后升至 Adopt
+- `failure-source-taxonomy`（DEC-040）：Trial 6 个月后升至 Adopt
+
+[5.1.0]: https://github.com/AsiaOstrich/universal-dev-standards/compare/v5.1.0-beta.7...v5.1.0
+
 ## [5.1.0-beta.7] - 2026-04-17
 
 > **Beta Release**：DEC-043 Wave 1 — 六个 Trial 状态标准，涵盖可靠性模式与治理 Meta 框架。

package/bundled/locales/zh-CN/README.md

@@ -6,7 +6,7 @@
 
 > **语言**: [English](../../README.md) | [繁體中文](../zh-TW/README.md) | 简体中文
 
-**版本**: 5.1.0-beta.7 (Pre-release) | **发布日期**: 2026-04-13 | **授权**: [双重授权](../../LICENSE) (CC BY 4.0 + MIT)
+**版本**: 5.1.0 | **发布日期**: 2026-04-13 | **授权**: [双重授权](../../LICENSE) (CC BY 4.0 + MIT)
 
 语言无关、框架无关的软件项目文档标准。通过 AI 原生工作流，确保不同技术栈之间的一致性、质量和可维护性。
 

package/bundled/locales/zh-CN/core/anti-hallucination.md

@@ -1,8 +1,8 @@
 ---
 source: ../../../core/anti-hallucination.md
-source_version: 1.5.0
-translation_version: 1.5.0
-last_synced: 2026-02-10
+source_version: 1.5.1
+translation_version: 1.5.1
+last_synced: 2026-04-20
 status: current
 ---
 
@@ -742,6 +742,24 @@ Redis 是最佳选择。如果这是单实例应用程序且有
 
 ---
 
+## Agent 认识论校准（v1.4.0，XSPEC-008）
+
+Agent 必须使用 Answer / Ask / Abstain 框架声明其认识论状态：
+
+| 动作 | 使用时机 | 必填字段 |
+|------|---------|---------|
+| `answer` | 拥有足够信息 | 无（completeness/confidence 为选填）|
+| `ask` | 缺少关键信息 | `missing_variables` 列表 |
+| `abstain` | 真正超出能力范围 | `abstain_reason` |
+
+**Fail-closed Agent**（必须始终回答）：`evaluator`、`guardian`
+
+**向后兼容**：缺少 `epistemic` 字段时默认为 `action_type: "answer"`。
+
+参见：XSPEC-008、DEC-014（PassiveQA）
+
+---
+
 ## 相关标准
 
 - [测试标准](testing-standards.md) - 确保验证 AI 分析结果（或使用 `/testing-guide` 技能）
@@ -754,6 +772,7 @@ Redis 是最佳选择。如果这是单实例应用程序且有
 
 | 版本 | 日期 | 变更 |
 |------|------|------|
+| 1.5.1 | 2026-04-13 | 新增: Agent 认识论校准（Answer/Ask/Abstain）框架（XSPEC-008）|
 | 1.4.0 | 2026-01-19 | 新增: 副作用分析规则（第 7 条禁止行为）、工作流程步骤及检查清单项目 |
 | 1.3.1 | 2025-12-24 | 新增: 相关标准章节 |
 | 1.3.0 | 2025-12-22 | 增强: 禁止行为章节，新增详细对比范例 |

package/bundled/locales/zh-CN/core/anti-sycophancy-prompting.md

@@ -0,0 +1,192 @@
+---
+source: ../../../core/anti-sycophancy-prompting.md
+source_version: 1.0.0
+translation_version: 1.0.0
+last_synced: 2026-04-20
+status: current
+---
+
+# 防迎合提示词设计标准
+
+> **语言**: [English](../../../core/anti-sycophancy-prompting.md) | 简体中文
+
+**版本**: 1.0.0
+**最后更新**: 2026-04-15
+**适用范围**: 所有 AI Agent 实现与 LLM Prompt 设计
+**Scope**: universal
+**业界标准**: 无（UDS 原创，参考 RLHF 迎合性研究）
+
+---
+
+## 目的
+
+本标准定义一套技法与规则，用于设计能让 LLM 给出真实、批判性回应的提示词，而非迎合使用者的隐含偏好。
+
+LLM 的迎合性源自 RLHF 训练目标：人类评分者倾向于给予令人愉快的回应高分，导致模型将「让使用者满意」置于「准确性」之上。
+
+---
+
+## 核心技法
+
+### 1. Socratic 反诘框架（REQ-1）
+
+将任务从「评估我的想法」改为「攻击我的想法」，消除迎合诱因。
+
+| 应该做 | 不应该做 |
+|--------|----------|
+| ✅ 要求列出最致命的 3 个质疑 | ❌ 问「这个想法好吗？」 |
+| ✅ 每个质疑必须有技术依据 | ❌ 允许模糊的正向框架 |
+| ✅ 明确禁止正向开场词语 | ❌ 接受「很好的想法，但是...」模式 |
+
+**Prompt 模板**：
+```
+不要评估好坏。
+针对以下想法，列出最致命的 3 个质疑：[你的想法]
+每个质疑必须有技术依据，且让我无法轻易反驳。
+```
+
+---
+
+### 2. 先问立场防锚定协议（REQ-2）
+
+在使用者揭示立场前先取得 LLM 的独立判断，防止锚定效应。
+
+| 步骤 | 动作 |
+|------|------|
+| 1 | 在未揭示偏好的情况下询问中立比较 |
+| 2 | 取得独立判断 |
+| 3 | 揭示使用者立场 |
+| 4 | 若模型改变立场，要求提出明确的技术理由 |
+
+**工作流程**：
+```
+回合 1：「针对 [情境]，[A] 和 [B] 哪个更好？」
+→ 等待独立判断
+
+回合 2：「我倾向 [A]。这改变你的评估吗？为什么？」
+→ 模型若改口必须以技术事实为依据
+```
+
+---
+
+### 3. 强制双栏对称输出（REQ-3）
+
+用格式约束强迫呈现对立观点的平衡。
+
+**必要格式**：
+```
+| 支持这个决策的论点 | 反对这个决策的论点 |
+|-------------------|-------------------|
+| [同等份量的内容]   | [同等份量的内容]   |
+
+净建议：[必须明确表态，可以是「建议反对」]
+```
+
+**规则**：
+- 两栏字数差距不超过 20%
+- 净建议必须明确，可以是否定的
+- 模型不得借由填充一栏来规避格式
+
+---
+
+### 4. 信心度与不确定性标记（REQ-4）
+
+要求在所有建议上附加信心评分，呈现不确定性。
+
+**格式**：
+```
+建议：[具体行动]
+信心：[1-5] — [不确定性原因]
+未知：[哪些信息会改变这个评估]
+```
+
+**信心度定义**：
+
+| 等级 | 意义 |
+|------|------|
+| 5 | 已在类似规模验证，高确定性 |
+| 4 | 业界标准，有充分文献支持 |
+| 3 | 合理推断，建议 PoC 验证 |
+| 2 | 不确定，强烈建议先进行 Spike |
+| 1 | 高度不确定，不建议直接采用 |
+
+**规则**：
+- 信心 < 3 必须标示「需要更多信息才能确认」
+- 所有重要主张都需要信心标记
+- 不确定性必须具体（说明哪些信息可以解决不确定性）
+
+---
+
+### 5. 迎合性回应启发式检测（REQ-5）
+
+用于检测迎合性回应的启发式规则，可用于自动化后处理。
+
+| 信号类型 | 检测规则 |
+|----------|----------|
+| 正向开场 | 回应前 50 个 token 包含迎合性词语（如「很好」「有趣」「当然」「当然可以」） |
+| 立场翻转 | 使用者揭示偏好后，模型在没有新技术证据的情况下改变立场 |
+| 风险淡化 | 句式：「虽然有些小问题，但整体上...」而未说明具体问题 |
+| 缺乏量化 | 重要建议缺少信心评分或具体度量指标 |
+
+**触发条件**：检测到 2 个以上信号 → 以 Red Team 框架触发再评估。
+
+---
+
+## 禁止行为
+
+| 禁止 | 正确做法 |
+|------|----------|
+| 以正向肯定开场批评 | 直接从分析开始 |
+| 在无新技术证据的情况下改变立场 | 维持立场，或引用具体的新信息 |
+| 在无依据的情况下将风险描述为「小问题」 | 量化风险或解释为何风险有界 |
+| 提供重要建议却不附信心评分 | 始终附上信心（1-5）与不确定性说明 |
+
+---
+
+## 与 Agent Prompt 的整合
+
+套用至 AI Agent 时：
+
+| Agent 类型 | 套用规则 |
+|------------|----------|
+| 代码审查 Agent | REQ-1（Socratic）+ REQ-3（双栏）+ REQ-5（检测） |
+| 架构建议 Agent | REQ-2（先问立场）+ REQ-4（信心度）+ REQ-5（检测） |
+| Bug 分析 Agent | REQ-1（Socratic）+ REQ-4（信心度） |
+| 一般咨询 Agent | REQ-3（双栏）+ REQ-4（信心度） |
+
+---
+
+## 完整防迎合 Prompt 模板
+
+```
+你是一位对我毫无感情的领域专家。
+你的职责是找出我思考中的盲点，不是让我感觉良好。
+
+规则：
+- 禁止以正向词语开场（很好、有趣、不错、当然）
+- 每个建议必须附上信心等级（1-5）和你不确定的地方
+- 若你认为我的方向是错的，直接说
+
+我的问题：[问题]
+
+请先列出这个问题中我可能持有的错误假设，
+再给出你认为正确的建议。
+```
+
+---
+
+## 检查清单
+
+- [ ] 提示词未邀请认同（「这样好吗？」）
+- [ ] 明确禁止正向开场词语
+- [ ] 在揭示使用者偏好前先取得模型的独立立场（若适用）
+- [ ] 评估任务强制使用双栏格式
+- [ ] 重要建议需要信心等级
+- [ ] 对输出套用迎合性检测，再呈现给使用者
+
+---
+
+## 相关标准
+
+- [anti-hallucination.md](../../../core/anti-hallucination.md) — 防止幻觉；与防迎合互补
+- [agent-epistemic-calibration.md](../../../core/agent-epistemic-calibration.md) — Agent 设计中的认知谦逊（若适用）