principle-outcome-oriented-execution

Prioritize the intended end state over transitional stability. Declare where temporary breakage is acceptable, keep high-signal checks on actively touched areas, and require full static and runtime verification at plan completion.

Use it for planned rewrites and migrations with explicit phase boundaries. It is designed for work where intermediate breakage is planned, scoped, and reversible, not for incremental bug fixes or live production patches.

Yes, when the breakage is planned, scoped, and reversible. The principle holds that keeping every intermediate step fully stable often creates temporary compatibility code that becomes long-lived debt.

Full static and runtime verification must run at plan completion. Final verification at explicit boundaries proves the target architecture is correct before the work is considered finished.

Avoid it for work without explicit phase boundaries or where intermediate states must remain continuously stable, such as zero-downtime production changes. It targets planned rewrites, not incremental maintenance.