principle-outcome-oriented-execution

Define explicit phase boundaries and converge on the target architecture rather than keeping every intermediate state stable. Accept planned, scoped, reversible breakage between phases, and run full static and runtime verification at plan completion.

Avoid throwaway compatibility code during planned rewrites with explicit phase boundaries, since temporary shims often become long-lived debt. Prioritize end-state integrity and prove correctness at verification boundaries instead.

Yes, intermediate breakage is acceptable when it is planned, scoped, and reversible. Declare where temporary breakage is allowed and keep high-signal checks running for actively touched areas while migrating.

Do not use it for unplanned changes or work without explicit phase boundaries. It is designed for deliberate rewrites and migrations where verification boundaries can be defined and enforced.

Full static and runtime verification must pass at plan completion before declaring done. Final verification proves the target architecture is correct, not just that intermediate steps were stable.