There is a persistent temptation to think that important knowledge becomes more useful when we gather it into one place.
Often it does.
Standards allow people who have never met to build compatible things. Procedures preserve lessons that would otherwise have to be rediscovered. Medical knowledge can move between hospitals. Engineering practices can travel between companies. A measurement made in one place can be understood somewhere else because people agreed in advance about what the units mean.
Civilization depends heavily on our ability to do this.
We observe many individual cases, find something that survives comparison and compress what we've learned into a form that can travel.
The interesting question is what happens next.
A rule, standard, policy or model is necessarily smaller than the collection of experiences from which it emerged. That's why it's useful. If a procedure required everyone applying it to personally relive every failure that contributed to its creation, we wouldn't have gained much by writing the procedure.
Compression lets learning travel farther than the people who originally did the learning.
Something is discarded in the process.
Usually that's intentional.
A building code doesn't need to preserve the personality of every engineer who contributed to it. A newspaper style guide doesn't need the complete history of every editorial argument that shaped each rule. A software interface becomes useful precisely because the person using it doesn't need to understand everything happening underneath.
Abstraction hides particulars so that attention can move somewhere else.
The danger begins when we forget that anything was hidden.
A rule that worked across a thousand previous cases encounters the thousand-and-first case, and something about this one is different. Perhaps the difference doesn't matter. Perhaps the person applying the rule simply doesn't understand why it exists. Perhaps allowing everyone to improvise would recreate exactly the failures the standard was designed to prevent.
Or perhaps the new case contains information the rule doesn't represent.
We can't know merely because somebody says, “This doesn't fit.”
The exception gets a hearing, not automatic authority.
That distinction matters because centralized knowledge and local judgment can each fail in opposite directions. A large institution can become so confident in its model that contradictory observations are treated as errors in the people reporting them. A local operator can become so confident in experience that every inconvenient standard looks like interference from people who don't understand the situation.
Both can be protecting accumulated knowledge.
Both can also be protecting themselves from correction.
What matters is whether the disagreement has somewhere to go.
Imagine a procedure developed after years of experience. Most of the time it works well, including in situations where an inexperienced person might otherwise make a predictable mistake. Someone eventually encounters a case where following the procedure appears to produce the wrong result.
One possibility is to let that person ignore the procedure whenever they feel like it.
Another is to insist that the procedure must be followed because it was written by people with greater expertise.
Neither response teaches us very much.
A better system preserves both pieces of information: this rule exists for reasons, and this case appears not to fit it.
Now we can investigate.
Maybe the exception disappears once the reason for the rule becomes clear. Maybe the procedure needs an additional condition. Maybe an unusual local circumstance requires a documented exception. Maybe the rule was once correct and the environment around it has changed enough that the original solution is now causing a different problem.
The important feature isn't whether authority began centrally or locally.
It's whether reality can still modify what the organization thinks it