Core Principles
Claiming completion without verification is a sign of dishonesty.
没有验证证据，就不能声称完成
Verification Gating
在声称任何状态或表达满意之前：
- Identify: what command/operation can prove this claim?
- Execute: run the complete verification operation
- Read: the complete output, check the results
- Verify: does the output confirm the claim?
- If no: state the actual status and evidence
- If yes: state the claim and evidence
- Only then: make the claim
Skipping any step = lying, not verification
## 常见验证场景
| 声称 | 需要的验证 | 不充分 |
|------|----------|--------|
| 章节完成 | 字数统计、结构检查、文件存在 | "应该写完了" |
| 引用真实 | DOI 可访问、CrossRef API 确认 | "看起来像真的" |
| 论点有支撑 | evidence map 中有段落级证据 | "这段写得像论文" |
| 格式正确 | 运行格式检查脚本 | 目测检查 |
| 无AI痕迹 | 运行风格检查脚本 | "读起来还行" |
| 文献搜索完成 | 结果数量、DOI 列表、JSON 文件存在 | "搜过了" |
| skill 改造完成 | 运行 `scripts/check_skill_integrity.ps1` | "文件都写了" |
| 初稿达到质量门 | 运行 `scripts/research_quality_gate.ps1` | 只运行 style_check |
## Red Flags - 停止
出现以下情况时，必须先验证：
- 使用"应该"、"可能"、"看起来"
- 在验证前表达满意（"好了！"、"完成！"）
- 准备提交/推送/合并而不验证
- 相信代理的成功报告
- 依赖部分验证
- 想着"就这一次"
- 疲劳想结束工作
- **任何暗示成功但没有运行验证的措辞**
## 借口与事实
| 借口 | 事实 |
|------|------|
| "应该行了" | 运行验证命令 |
| "我很确信" | 确信 ≠ 证据 |
| "就这一次" | 没有例外 |
| "格式检查过了" | 格式检查 ≠ 内容正确 |
| "代理说成功了" | 独立验证 |
| "我累了" | 疲劳不是借口 |
| "部分检查够了" | 部分证明不了什么 |
## 关键验证模式
### 章节完成验证
✅ [Run word count] [See: 3000 words] "Chapter word count meets standard" ✅ [Check file exists] [See: chapters/01-introduction.md exists] "Chapter file has been created" ✅ [Run format check] [See: 0 errors] "Format is correct" ❌ "It should be done" / "It looks complete"
### 引用验证
✅ [Call CrossRef API] [See: DOI exists, information matches] "Citation verified" ✅ [Search original source] [Find: author, journal, year consistent] "Citation is real" ❌ "The citation looks correct" / "It should be real"
### 论点支撑验证
✅ [Check evidence-map] [See: each gap claim corresponds to 2 sources] "Research gap is supported by literature" ✅ [Check citation slot] [See: paragraph P2 uses FL-05 + FL-07] "Citation location is clear" ❌ "The related work looks complete" / "This paragraph has an academic feel"
### Skill 完整性验证
```powershell
powershell -ExecutionPolicy Bypass -File scripts/check_skill_integrity.ps1
Used to confirm that newly added skills, routing, verification scripts, and key gates still exist.
Manuscript quality gate verification
powershell -ExecutionPolicy Bypass -File scripts/research_quality_gate.ps1 -ProjectPath <paper-project>
Used to check citation coverage, main text contamination, listification, placeholder strategy, figure data manifest, and evidence map. Before submission add -Submission, unfilled placeholders are prohibited.
Literature search verification
✅ [检查 JSON 文件] [看到：20 条结果，每条有 DOI] "搜索完成"
✅ [验证 BibTeX 输出] [看到：可解析，无错误] "BibTeX 有效"
❌ "搜过了" / "应该有结果"
Verification checklist
Before completing each task, you must verify:
- Ran the verification command
- Read the complete output
- Confirmed the results support the claim
- Did not rely on "should" or "probably"
- Evidence is presented in the current message
Why this matters
From actual failure cases:
- Fabricated citations led to paper retraction
- Chapter word count not meeting standard led to rework
- Format errors led to submission failure
- Obvious AI traces led to reviewer doubts
Bottom line
There are no shortcuts in verification.
Run the command. Read the output. Only then can you claim the result.
This is non-negotiable.