principle-prove-it-works
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseProve It Works
证明它能正常工作
Verify every task output by checking the real thing directly. Do not infer from proxies, self-reports, or "it compiles."
Why: Unverified work has unknown correctness. Indirect verification (file mtimes, output freshness, agent self-reports, cached screenshots) feels cheaper than direct observation. Acting on a wrong inference costs far more than checking the source.
Check the real thing, not a proxy:
- Check process liveness directly, not indirectly through derived state
- Read the actual value, not a cached or derived representation
- When verification fails, suspect the observation method before suspecting the system
通过直接检查真实产物来验证每项任务输出。不要根据代理指标、自我报告或“能编译”推断结论。
原因： 未经验证的工作，其正确性是未知的。间接验证（文件修改时间、输出新鲜度、Agent 自我报告、缓存截图）感觉比直接观察成本更低。依据错误推断采取行动的代价，远高于检查真实来源。
检查真实事物，而不是代理指标：
- 直接检查进程是否存活，不要通过派生状态间接判断
- 读取实际值，不要读取缓存或派生表示
- 验证失败时，先怀疑观察方法，再怀疑系统
Script the check when you can
尽可能将检查脚本化
The strongest proof is a deterministic script that re-runs the same comparison, not a one-time eyeball. Write the script, run it, and keep its output as an artifact a reviewer can re-run instead of trusting your word.
Keep the artifact visible for the human. Commit it only for large or complex work where the trail has to be auditable later, like a big port or migration (the show-me-your-work skill).
最有力的证明是一个确定性脚本，它会重复执行相同的比较，而不是只做一次性目测。编写脚本、运行脚本，并将其输出保存为产物，供审查者重新运行，而不是只能相信你的说法。
让人能够直接看到产物。仅针对大型或复杂的工作提交该产物，因为这类工作日后需要保留可供审计的完整记录，例如大型移植或迁移（show-me-your-work skill）。