principle-outcome-oriented-execution

1# Outcome-Oriented Execution
2 
3Optimize for the intended, verifiable end state rather than preserving smooth intermediate states.
4 
5**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.
6 
7**Core rule:**
8- Prioritize end-state integrity over transitional stability
9- Intermediate breakage is acceptable when it is planned, scoped, and reversible
10 
11**Guardrails:**
12- Use this for planned rewrites and migrations with explicit phase boundaries
13- Declare where temporary breakage is acceptable
14- Keep high-signal checks for actively touched areas while migrating
15- Require full static and runtime verification at plan completion