Code is Law
Updated 2026-08-04
INTRODUCTION
English translation pending.
CORE DEFINITION
A thesis arguing that behavior in cyberspace is regulated by four forces, with architecture, meaning code, being the most consequential. Law states what is permitted, social norms what is expected, and markets what is priced, but code determines what is technically possible at all. Because architecture is written by a small number of developers and is costly to change, its regulatory power is often stronger than legislation. The implication is that technical design choices are political acts and therefore deserve the scrutiny that law receives.
SCAFFOLDING EFFECT
Reduce cognitive load
- Layer choice: decide whether a rule belongs in a user agreement or in the code that enforces it. - Default design: recognize that the default option governs most behavior, so choose it deliberately. - Accountability note: treat architecture decisions as legislation and document who made them and why.
Anchor fast decisions
A legal rule requires detection and enforcement, so it binds only when violation is observed and sanctioned. An architectural constraint binds at the moment of action, because the prohibited option does not exist in the interface. That is why a limit written into the code is obeyed without enforcement, and why the small group who write the architecture hold regulatory power that is rarely audited. The mechanism is the substitution of capability limits for conduct rules.
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/Lawrence_Lessigverified
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