principle-outcome-oriented-execution

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

Use it for planned rewrites and migrations with explicit phase boundaries. It is not suited for incremental changes to live systems where continuous stability is required, since it permits planned intermediate breakage.

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

Full static and runtime verification at plan completion is required. Each phase boundary acts as an explicit verification checkpoint, and no work is declared done until final verification passes.

Avoid it for unplanned or exploratory changes, hotfixes on production systems, or work without clear phase boundaries. It is designed for deliberate rewrites where the target end state is known and verifiable.