principle-outcome-oriented-execution

Converge on the target architecture instead of preserving smooth intermediate states. Declare where temporary breakage is acceptable, keep it scoped and reversible, and run full static and runtime verification before declaring the migration done.

Use it for planned rewrites and migrations with explicit phase boundaries. It is not suited for incremental changes to stable production systems where intermediate breakage is not acceptable or reversible.

Yes, when it is planned, scoped, and reversible. The principle requires declaring acceptable breakage zones upfront and maintaining high-signal checks for actively touched areas while migrating.

Full static and runtime verification at plan completion is required. Final verification must always run before declaring done, ensuring the target architecture is proven correct at explicit verification boundaries.

Avoid it for work without explicit phase boundaries, unplanned changes, or systems where any intermediate instability is unacceptable. It is designed for deliberate rewrites, not continuous incremental maintenance.