Outcome-Oriented Execution

Optimize for the intended, verifiable end state rather than preserving smooth intermediate states.

Why: Keeping every intermediate step fully stable often creates temporary compatibility code that becomes long-lived debt. Converge on the target architecture and prove correctness at explicit verification boundaries.

Core rule:

• Prioritize end-state integrity over transitional stability
• Intermediate breakage is acceptable when it is planned, scoped, and reversible

Guardrails:

• Use this for planned rewrites and migrations with explicit phase boundaries
• Declare where temporary breakage is acceptable
• For migrations with old and new contracts, invoke /pstack-principle-migrate-callers-then-delete-legacy-apis for compatibility strategy and verification-unit gates. Transitional breakage stays inside the declared unit; required release boundaries still pass.
• Keep high-signal checks for actively touched areas while migrating
• Require full static and runtime verification at plan completion