Error background articles

Each article covers one error family that appears across many analyzed libraries — the mechanism behind it, the causes the records agree on, and where the libraries differ. They are generated from the documented records and grow as the corpus does.

• The base Error class: deliberate library guards and refused operations
  This family is the generic Error that a library throws on purpose, from its own code, when a caller violates a precondition it is not willing to paper over. A developer meets it not because of a type slip or a runtime engine fault, but because the library has decided that a configuration value, a payload shape, an environment, or a security posture is wrong enough that guessing would be worse than stopping. Across 54 repositories these throws share one shape — a synchronous, hand-worded message at a trust boundary — while differing widely in what triggered them. (3,783 records across 54 repos)

Looking for a specific failure class? The guides go deeper on the big ones.