Load-Bearing Rule

Every mature library contains rules that matter enormously and look unremarkable — a definition three other skills assume, a scope boundary that quietly prevents a class of request from reaching a domain it should not. Their importance is invisible in isolation and only appears in the graph. The opposite category is equally common: rules added for a circumstance that has passed, still loading, consuming context budget and occasionally contradicting something newer. Without relationship data both look identical, which is why organizations either delete nothing or delete carelessly.

Because the Centralpoint corpus is maintained with its dependencies explicit, load-bearing and vestigial rules are distinguishable. That distinction is what allows a library to be pruned rather than only extended — and pruning matters, because every rule loaded occupies budget that could have gone to retrieved content or to a rule that was actually needed.