Krypton Planning

Krypton Planning turns a request into an implementation plan that names the outcome, truth owner, contract, cutover, and acceptance evidence before anyone writes code.

Core Rule

Do not treat a task list as a plan. A Krypton plan is ready only when it answers:

What outcome are we serving?
What current behavior is being replaced, redirected, deleted, or demoted?
Who owns the truth?
What contract crosses the boundary?
What is the smallest high-value slice?
What proves the result from the target person's perspective?
What kill criteria stop duplicate paths from living forever?

If ownership, cutover, contract, or evidence is fuzzy, stop and map before planning.