Hyrum's Law
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
“When an API has enough users, what you promise in the contract doesn't matter: all observable behaviors of your system (even bugs or side effects) will be depended on by some users.” -
SCAFFOLDING EFFECT
Reduce cognitive load
The curse of implicit dependencies. - This explains why reform is so difficult. You think you're just fixing a “bug,” only to find that this “bug” is not only regarded as a “feature” by employees but also becomes a core pillar of business processes. In complex systems, there is no “harmless change.” Any status quo (even a bad one) is the foundation on which some ecosystem survives.
Anchor fast decisions
Hyrum's Law: When an API has enough users, the behaviors you promise in the contract matter less than the behaviors that are actually depended on in practice—any observable output or side effect will be depended on by someone, and thus cannot be safely changed.
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/APIverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS