principle-outcome-oriented-execution

Converge directly on the target architecture and verify correctness at explicit phase boundaries instead of keeping every intermediate state stable. Declare where temporary breakage is acceptable and keep it scoped and reversible.

Intermediate breakage is acceptable when it is planned, scoped, and reversible within a migration that has explicit phase boundaries. Always declare the breakage zones upfront and run full verification before declaring the work done.

Avoid this approach for changes without explicit phase boundaries or where continuous stability is mandatory, such as live production hotfixes. It is designed for planned rewrites and migrations, not incremental maintenance work.

Full static and runtime verification at plan completion is required. Keep high-signal checks running for actively touched areas throughout the migration, then prove end-state correctness at the final boundary.

Keeping every intermediate step fully stable requires temporary compatibility code that often survives long after the migration ends. Prioritizing end-state integrity avoids this scaffolding becoming permanent debt.