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
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
以预期且可验证的最终状态为目标，而不是维持平滑的中间状态。
原因： 始终保持每个中间步骤完全稳定，往往会引入临时兼容性代码，而这些代码最终会演变成长期技术债。应收敛到目标架构，并在明确的验证边界证明其正确性。
核心规则：
  • 优先保证最终状态的完整性，而非过渡期间的稳定性
  • 如果中间状态的中断是计划内、范围明确且可逆的，则可以接受
护栏：
  • 适用于具有明确阶段边界的计划性重写和迁移
  • 明确声明可接受临时中断的范围
  • 迁移期间，仅对正在 actively touched 的区域保留高信号检查
  • 计划完成时，要求进行完整的静态验证和运行时验证