The argument
Nobody Here Made This Decision
A legacy decision becomes a current control problem when the organization preserves its behavior but loses its rationale, owner, and testable boundary.
The field pattern
The rule predates the current team, ticketing system, cloud account structure, and network diagram. Everyone agrees it looks strange. Nobody can prove what will break if it disappears, so the safest short-term action is always to leave it alone.
Why it matters
Inheritance is normal. Unowned inheritance is not. The current organization remains responsible for understanding and controlling the environment it operates, even when it did not create every decision.
Fear of change is evidence of missing knowledge. Leaving the item in place may be reasonable temporarily, but that choice should create an owner, a bounded investigation, and a decision date—not another year of folklore.
Questions that expose the Wack
- Who owns the risk today, regardless of who created the configuration?
- What observable behavior might depend on it?
- Can telemetry replace fear with a measured dependency inventory?
- What is the date for a new keep, change, or remove decision?