verification-before-completion
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese完成前驗證
Pre-Completion Verification
概述
Overview
在沒有驗證的情況下聲稱工作已經完成是不誠實的，而不是效率。
核心原則： 證據先於主張，始終如此。
**違反本規則的字面意義即違反本規則的精神。 **
Claiming work is done without verification is dishonesty, not efficiency.
Core Principle: Evidence precedes claims, always.
Violating the letter of this rule is violating the spirit of this rule.
鐵律
Iron Rule
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE如果您沒有運行此訊息中的驗證命令，則不能聲稱它通過了。
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCEIf you haven't run the verification commands in this message, you cannot claim it passed.
門功能
Gate Function
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifyingBEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifying常見故障
Common Failures
| 索賠 | 需要 | 還不夠 |
|---|---|---|
| 測試通過 | 測試命令輸出：0 次失敗 | 上一次運行，“應該通過” |
| 棉絨清潔 | Linter 輸出：0 個錯誤 | 部分研究、推斷 |
| 建置成功 | 建置指令：exit 0 | Linter 通過，日誌看起來不錯 |
| 錯誤已修復 | 測試原始症狀：通過 | 代碼已更改，假設已修復 |
| 回歸測試有效 | 紅綠循環驗證 | 測試一次通過 |
| 代理完成 | VCS diff 顯示更改 | 代理報告“成功” |
| 滿足要求 | 逐行檢查表 | 測試通過 |
| Claim | Required | Not Enough |
|---|---|---|
| Tests Pass | Test command output: 0 failures | Last run, "should pass" |
| Linter Clean | Linter output: 0 errors | Partial investigation, inference |
| Build Success | Build command: exit 0 | Linter passed, logs look good |
| Bug Fixed | Test original symptom: passes | Code changed, assumed fixed |
| Regression Test Valid | Red-green cycle verification | Test passes once |
| Agent Completed | VCS diff shows changes | Agent reports "success" |
| Requirements Met | Line-by-line checklist | Tests passed |
危險信號 - 停止
Red Flags - Stop
- 使用“應該”、“可能”、“似乎”
- 在驗證之前表達滿意（“太棒了！”、“完美！”、“完成！”等）
- 即將工作/勞力/PR，消耗驗證
- 信任代理成功報告
- 依賴部分驗證
- 想著“就這一次”
- 累了並且想要結束工作
- 任何暗示成功但未運行驗證的措辭
- Using "should", "might", "seems"
- Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.)
- Preparing work/labor/PR, skipping verification
- Trusting agent success reports
- Relying on partial verification
- Thinking "just this once"
- Tired and wanting to finish work
- Any wording implying success without running verification
合理化預防
Rationalization Prevention
| 對不起 | 現實 |
|---|---|
| “現在應該工作了” | 運行驗證 |
| 「我有信心」 | 信心≠證據 |
| 「就這一次」 | 無一例外 |
| “Linter 通過” | Linter ≠ 編譯器 |
| 《代理說成功》 | 獨立驗證 |
| “我累了” | 疲憊≠藉口 |
| 「部分檢查就夠了」 | 部分證明不了什麼 |
| 「不同的詞語，因此規則不適用」 | 精神重於文字 |
| Excuse | Reality |
|---|---|
| "It should work now" | Run verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ compiler |
| "The agent said it succeeded" | Independent verification |
| "I'm tired" | Fatigue ≠ excuse |
| "Partial check is enough" | Partial proves nothing |
| "Different wording, so the rule doesn't apply" | Spirit over letter |
關鍵模式
Key Patterns
測試：
✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"回歸測試（TDD紅-綠）：
✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)建造：
✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)要求：
✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"代理委託：
✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent reportTesting:
✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"Regression Testing (TDD Red-Green):
✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)Build:
✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)Requirements:
✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"Agent Delegation:
✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent report為什麼這很重要
Why This Matters
24次失敗記憶：
- 你的人類伴侶說“我不相信你”——信任被打破
- 未定義的函數已發布 - 會崩潰
- 缺少已交付的需求 - 功能不完整
- 時間浪費在錯誤完成→重定向→返工上
- 違規：“誠實是核心價值觀。如果你撒謊，你就會被取代。”
24 Failure Memories:
- Your human partner says "I don't believe you" — trust broken
- Undefined function released — will crash
- Delivered requirement missing — feature incomplete
- Time wasted on false completion → redirection → rework
- Violation: "Honesty is a core value. If you lie, you're replaced."
何時申請
When To Apply
**總是在：**之前
- 成功/完成聲明的任何變化
- 任何滿意的表達
- 關於工作狀態的任何積極陳述
- 承諾、公關創建、任務完成
- 移至下一個任務
- 委託給代理人
規則適用於：
- 準確的短語
- 釋義和同義詞
- 成功的影響
- 任何表明完成/正確性的通信
Always before:
- Any success/completion claim
- Any expression of satisfaction
- Any positive statement about work status
- Commitment, PR creation, task completion
- Moving to next task
- Delegating to agent
Rule applies to:
- Exact phrases
- Paraphrases and synonyms
- Implications of success
- Any communication indicating completion/correctness
底線
Bottom Line
**驗證沒有捷徑。 **
運行命令。讀取輸出。然後領取結果。
這是沒有商量餘地的。
There are no shortcuts to verification.
Run the command. Read the output. Then claim the result.
This is non-negotiable.