Least Capability Principle
Updated 2026-08-22
INTRODUCTION
English translation pending.
CORE DEFINITION
The principle, stated by Tim Berners-Lee for the World Wide Web, recommends selecting the least powerful language or system capable of meeting the requirement. More expressive tools, such as Turing-complete languages, can compute anything, but that very power makes them hard to analyze, verify and secure. A declarative or restricted tool does less, yet what it does is fully predictable from its specification. Choosing HTML over JavaScript, or configuration over code, trades unreachable generality for stability, analyzability and long-term maintainability.
SCAFFOLDING EFFECT
Reduce cognitive load
- Ask for weaker: before choosing, ask whether a far less expressive tool would suffice. - Prefer the declarative: pick configuration and static markup over imperative programming code. - Trade power for safety: accept less capability in exchange for analysis and long-term stability.
Anchor fast decisions
Expressive power and analyzability trade off directly, because a system that can compute arbitrary behavior cannot be statically checked for what it will do. A restricted tool's behavior is determined by its specification, so its output can be predicted and composed without running it. The weaker tool also exposes fewer surfaces for error and attack, which is why limiting capability raises stability and maintainability rather than lowering capability as an end in itself.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Principle_of_Least_Powerverified
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