Chesterton's Fence Principle

There is a concept known as Chesterton's Fence - that you shouldn't take down a fence someone else put up until you know why they put it up, or more generally if you don't understand why something was previously considered a good solution to a problem, then it's possible you don't understand the problem it was meant to solve.

You seem to be hinting to Chesterton's fence [0].[0]: https://fs.blog/2020/03/chestertons-fence/

For those wondering, this refers to Chesterton's Fence: https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_...

The difference is Chesterton's fence: when you encounter something seemingly pointless you should learn why it was there before you consider removing or changing it.

The Chesterton fence argument is that you need to understand why the fence is there. If you do understand it, and still remove it, it doesn't say that's bad.

This is the chesterton's fence. Don't remove the barrier until you understood why the barrier was there first.

It's the corollary to Chesterton's Fence - don't remove it until you know why it's there, but also investigate why it's there.

Chesterton’s fence isn’t “respect it forever” or “spend infinite resources”. It’s “don’t tear it down until you understand why it’s there”. The whole point is to avoid breaking something whose purpose you haven’t yet understood, because the original builders might have had a good reason that isn’t obvious to you. Once you’ve understood it, you’re free to remove it if that reason no longer applies.

This is more specifically known as Chesterton’s Fence:https://en.m.wikipedia.org/wiki/Chesterton%27s_fence

It's essentially the Chesterton's Fence principle.