principle-outcome-oriented-execution

What problem does it solve? Planned rewrites and migrations often accumulate throwaway compatibility code because teams try to keep every intermediate state fully stable, turning temporary scaffolding into long-lived technical debt. ## Core Features & Use Cases - End-State Prioritization: Converges work on the intended target architecture instead of preserving smooth intermediate states. - Scoped Breakage Policy: Permits intermediate breakage only when it is planned, scoped, and reversible, with explicit declarations of where it is acceptable. - Verification Boundaries: Requires full static and runtime verification at plan completion before declaring the work done. - Use Case: During a multi-phase migration from a legacy module to a new architecture, apply this principle to delete old code paths directly rather than writing adapter layers, then run full verification at the final phase boundary. ## Quick Start Apply the outcome-oriented execution principle to plan this migration so we converge on the target architecture with verification at each phase boundary.