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 ensure it stays scoped and reversible.

Intermediate breakage is acceptable when it is planned, scoped, and reversible within a migration that has explicit phase boundaries. It should never be used as an excuse to skip final verification of the end state.

Avoid this approach for unplanned changes, hotfixes on live systems, or work without explicit phase boundaries. It is designed for deliberate rewrites and migrations where verification gates can be defined in advance.

Run full static and runtime verification at plan completion before declaring done. Keep high-signal checks active for actively touched areas throughout the migration to catch regressions early.

Temporary shims built to keep intermediate states stable often survive past the migration because removing them feels risky. Prioritizing end-state integrity avoids creating this throwaway code in the first place.