Keep a direction that was rejected in strategy from quietly re-entering through execution, optimization, renamed tactics, or familiar channel logic.
Use when
A direction has been rejected but work keeps re-entering through execution, “optimization,” or a more convenient name.
What it prevents
A rejected decision from remaining alive under tactical language until it quietly becomes the strategy again.
Run it
- Name the rejected direction exactly.
- State the evidence and condition that killed it.
- Name the channels or execution choices most likely to smuggle it back.
- Inspect the current plan for renamed versions of the same logic.
- Remove the re-entry or formally reopen the decision with new evidence.
Redline example
Celebrity modernization was rejected for the cycle. It returned as “launch amplification,” “brand consistency,” and “a limited partner moment.” The names changed; the permission and continuity problem did not. It either stays rejected or the team reopens the strategy and shows the new evidence.
Your live decision
Write the rejected direction, the disguised re-entry, and the evidence required before it can be reconsidered.
Route next
Use FN14 / Direction Portfolio to preserve the original rejection and FN24 / Continuity Gap Checklist if the re-entry appears during handoff.
Stop rule
A rejection may change when genuinely new evidence or conditions arrive—not because execution finds it easier or more familiar.
Core Field Read update
Record the rejected logic, disguised re-entry, current status, and the decision to remove or formally reopen it.