Back to Details

principle-outcome-oriented-execution

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Outcome-Oriented Execution

面向结果的执行

Optimize for the intended, verifiable end state rather than preserving smooth intermediate states.
Why: Keeping every intermediate step fully stable often creates temporary compatibility code that becomes long-lived debt. Converge on the target architecture and prove correctness at explicit verification boundaries.
Core rule:
  • Prioritize end-state integrity over transitional stability
  • Intermediate breakage is acceptable when it is planned, scoped, and reversible
  • Always run final verification before declaring done
Guardrails:
  • Use this for planned rewrites and migrations with explicit phase boundaries
  • Declare where temporary breakage is acceptable
  • Keep high-signal checks for actively touched areas while migrating
  • Require full static and runtime verification at plan completion
以预期的、可验证的最终状态为优化目标，而非维持平滑的中间状态。
原因： 让每一个中间步骤都保持完全稳定，往往会产生临时兼容代码，而这些代码最终会变成长期的技术债务。聚焦于目标架构，并在明确的验证边界处证明正确性。
核心规则：
  • 优先考虑最终状态的完整性，而非过渡阶段的稳定性
  • 当中间阶段的中断是有计划、有范围且可回滚时，这种中断是可接受的
  • 在宣告完成前，务必执行最终验证
防护措施：
  • 将此方法用于有明确阶段边界的规划重写与迁移工作
  • 明确声明哪些临时中断是可接受的
  • 在迁移过程中，对频繁改动的区域保持高信号检查
  • 在计划完成时，要求进行完整的静态与运行时验证